| Author |
Message
|
| pcrparimi |
 Posted: Thu Dec 27, 2001 5:23 am Post subject: |
 |
|
Apprentice
Joined: 09 Oct 2001
Posts: 43
Location: NY
|
Hi,
is there any difference between using the runmqlsr and Start listener methods. if so when do we use them.
Thanks,
Poornachandra Rao |
|
| Back to top |
|
 |
| middlewareonline |
| Posted: Thu Dec 27, 2001 10:30 am Post subject: |
|
|
Acolyte
Joined: 09 Jul 2001
Posts: 73
|
usually you will include runmqlsnr in the stratup script of the system (ex. init.conf). Start Listerner is more interactive way of starting the listener.
MiddlewareOnline.com
_________________
---------------------------------------------
IBM & SUN (J2EE) Certified Consultants,
http://www.MiddlewareOnline.com
A "SARVAM" Online Portal
http://www.SARVAM.com
--------------------------------------------- |
|
| Back to top |
|
|
| dgolding |
| Posted: Fri Dec 28, 2001 1:01 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
Sorry to be pedantic about this, but not quite..... 
runmqlsr IS the interactive way of starting the listener, from a command (DOS or Unix) level.
The "init.conf" you are referring to are the unix inetd.conf and services files in /etc. This I suppose is non-interactive - the inetd process starts up the channel program, so it IS the listener. No batteries required.
I don't know how RUNMQSC "under the hood" starts the listener program when you do a START LISTENER - I think it justs does a "runmqlsr" anyway. The BIG drawback is that you can't specify a port number with the START LISTENER command - it assumes 1414, usually okay unless you have more than one queue manager.
You can put runmqlsr commands in a batch script, but Windows NT will automatically slap the listener startup in if the queue manager startup is automatic on system startup.
Somebody mentioned something about performance issues with inetd.conf versus runmqlsr. I can't remember the issue to be honest but it had something to do with multi-threading. Have a look in the archives, it's in there somewhere!
HTH |
|
| Back to top |
|
|
| leot |
| Posted: Tue May 20, 2003 7:11 am Post subject: |
|
|
Novice
Joined: 21 Apr 2002
Posts: 24
Location: NYC
|
The runmqlsr is a bit problematic in that it blocking call, and therefore is diffcult to use in a script where you want to do other things.
Am I mistaken, or is there a workaround for this problem?
Thanks,
- Leo |
|
| Back to top |
|
|
| bower5932 |
| Posted: Tue May 20, 2003 8:24 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
When I run it on Windows, I put a start in front of it:
start runmqlsr -t tcp -p 1414 -m my.qmgr
I think you put an & (ampersand) at the end of the command in Unix? |
|
| Back to top |
|
|
| leongor |
| Posted: Wed May 21, 2003 12:53 am Post subject: |
|
|
Master
Joined: 13 May 2002
Posts: 264
Location: Israel
|
On Unix start listener with nohup :
nohup runmqlsr -tTCP -p1414 -mQMGR &
_________________
Regards.
Leonid.
IBM Certified MQSeries Specialist. |
|
| Back to top |
|
|
| Leafar |
| Posted: Thu May 22, 2003 7:10 am Post subject: |
|
|
Acolyte
Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires
|
On Unix, if you don't want use nohup, you cau use this
(runmqlsr -t tpc -p 1414 -m QMGR &)
The () unattach the process of the terminal
you can use it to run other process in background
Saludos
Rafael |
|
| Back to top |
|
|
| jsware |
| Posted: Tue May 27, 2003 10:19 am Post subject: |
|
|
Chevalier
Joined: 17 May 2001
Posts: 455
|
You can specify the port number "START LISTENER" uses by editing the qm.ini file and adding:
At the bottom. |
|
| Back to top |
|
|
| jackie |
| Posted: Thu Jun 05, 2003 10:54 am Post subject: |
|
|
Novice
Joined: 01 Jun 2003
Posts: 20
Location: NYC
|
when you are start queuemanager in NT, does it start to use the port 1414 anyway? If not, how we can define the port number to specific queue manager? or, "START runmqlsr -t TCP -t 1414 -m ... " has to be used to tie the port to the queuemanger?
thanks, |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Jun 05, 2003 11:01 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Jackie:
To start a listener for a Queue Manager:
Start -> Programs -> IBM WebSphere MQ -> WebSphere MQ Services
Clikc on the Queue Manager on which you want to start the listener. If there is a listener already created for that Queue Manager it'll be listed in the right hand pane. Or else
Right click on the Queue Manager -> New -> Listener
Select the parameters tab to specify the port.
-------
Venny |
|
| Back to top |
|
|
| jackie |
| Posted: Thu Jun 05, 2003 11:55 am Post subject: |
|
|
Novice
Joined: 01 Jun 2003
Posts: 20
Location: NYC
|
Venny, on again, great. However, if you want to specify in script, where you have to put "runmqlsr" in what order.
For example,
1. create queuemgr
2. runmqlsr -p 2000 for example
3. start queuemgr
or
1,3,2.
thanks in advance |
|
| Back to top |
|
|
| mqonnet |
| Posted: Thu Jun 05, 2003 11:58 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Should work either way.
Cheers
Kumar |
|
| Back to top |
|
|
| jackie |
| Posted: Fri Jun 06, 2003 7:26 am Post subject: |
|
|
Novice
Joined: 01 Jun 2003
Posts: 20
Location: NYC
|
However, even though I did run "runmqlst -t TCP -p 2000 ..." for the first qmgr and "runmqlsr -t TCP -p 2010 ... " for the second qmgr, in NT, it apparently does not take those port paramters.
Once those qmgrs up and running, and when I did check MMC, it still either points to 1414 or has blank. Any ideas? |
|
| Back to top |
|
|
| mqonnet |
| Posted: Fri Jun 06, 2003 10:08 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
When you say, " it apparently does not take those port paramters" what do you mean. Does it mean that when you issue runmqlsr with those ports, you get back a message saying could not bind to that port???
As for what you see in MMC, my guess is that since you did not change the port numbers from nor the mq explorer, nor the registry, but runmqlsr, the port numbers are not seen there. I dont think you can EVER match the port numbers that you see in mqexplorer and the one that you issue on runmqlsr command.
Cheers
Kumar |
|
| Back to top |
|
|
| jackie |
| Posted: Fri Jun 06, 2003 10:26 am Post subject: |
|
|
Novice
Joined: 01 Jun 2003
Posts: 20
Location: NYC
|
exactly as you said. Then, how I can do fix the port number using script and using runmqlsr command with -p option.
Since I would like to use script, I found out runmqlsr does not do the job. thanks for your input. Any better way so that I can use script instead of relying upon MMC or snap-in.??? |
|
| Back to top |
|
|
|
|
