| Author |
Message
|
| _novice_ |
 Posted: Fri Oct 22, 2004 11:20 am Post subject: difference between runmqlsr command and start listener scrip |
 |
|
Novice
Joined: 22 Oct 2004
Posts: 15
|
Env: windows 2K
The channel seems to be running properly when I start a listener with
runmqlsr -q <qmname> -t TCP -p 1450
But when I run listener using
runmqsc <qmname>
start listener trptype(tcp)
The channel is not running.
I either get
"AMQ9514: Channel 'TO.Q1' is in use" when I pull down the listener and start up again
or
AMQ9202: Remote host 'LOCALHOST (127.0.0.1) (1500)' not available, retry later.
when I do ping channel(<channel_name>)
Also the method of specifying the port number is not availble as a script except on Z/OS.. so how do u guys start a listener using runmqsc on UNIX/windows without specifying a port number..? And if the port number is not specified do u get to start the listener properly..? |
|
| Back to top |
|
 |
| clindsey |
| Posted: Fri Oct 22, 2004 12:29 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
On Windows, define and start the listener as a service so it will survive a logoff. Define it though the GUI or from command line with amqmdain. It will start when you start the queue manager.
On unix, start it with "nohup runmqlsr -t tcp -m xxxx -p 1450 &". You can put this in your start script.
Charlie |
|
| Back to top |
|
|
| _novice_ |
| Posted: Fri Oct 22, 2004 1:58 pm Post subject: |
|
|
Novice
Joined: 22 Oct 2004
Posts: 15
|
So what is the difference between
1. runmqsc xxxx
start listener -t(tcp)
end
and
2. norunmqlsr -m xxxx -t tcp -p yyyy
coz in option 1 we cannot specify the port number on non-Z/OS systems and which port does the listener run on in that case ? Does option 1 work well ..?
coz when I used option 1 the channels were not working well. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Oct 22, 2004 2:10 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Well not having ever used option 1 "start listener -t(tcp)" I would have to assume that the port would default to 1414. I haven't worked much with MQ on the z/OS platform so I really can't tell you the difference.
I have always used the runmqlsr on Microsoft, AIX and Solaris platforms.
Oh and by the way, looks like on my XP box the syntax for the command is more like:
| Code: |
| START LISTENER TRPTYPE(TCP) |
but there is still not option to specify a port.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Oct 23, 2004 1:04 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Guys
For windows I don't know. Must be in some registry settings
For distributed environments (unix) you don't need the port if you specified it in qm.ini
So yes you could start the listener from runmqsc. However I would not recommend it as it limits some of the options for security.
i.e. you could have multiple lsrs for the same qmgr with # port numbers run by diff users having diff permissions.....
Best option under Unix is
<nohup> runmqlsr -m QMGR -t tcp -p port# &
Enjoy  |
|
| Back to top |
|
|
|
|
