| Author |
Message
|
| bbburson |
 Posted: Wed Oct 25, 2006 7:21 am Post subject: runmqchi, runmqlsr: what is -r argument for? |
 |
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
I've observed on my WMQ v6, HP-UX 11.11 system that runmqchi and runmqlsr are being run with a new argument -r:
| Code: |
ps -ef|grep runmq
mqm 29586 29584 0 11:05:05 ? 0:02 /opt/mqm/bin/runmqchi -m QmgrName -r
mqm 29588 29584 0 11:05:06 ? 0:00 /opt/mqm/bin/runmqlsr -r -m QmgrName -t TCP -p 1414 -i xx.xx.xx.xx |
This argument did not show up in WMQ 5.3 and is not documented that I can find. Any idea what it indicates? I am using a listener object to start the listener, by the way.
I don't have WMQ 6 on Sun or AIX yet so I don't know if this argument shows up on those platforms as well. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Oct 25, 2006 7:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's probably what allows the queue manager to control the service once it's started.
I don't think it's actually a documented flag.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 25, 2006 2:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
It's probably what allows the queue manager to control the service once it's started.
I don't think it's actually a documented flag. |
I believe I saw it somewhere in the doc.
It is meant to register the listener with the qmgr...?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Mon Oct 30, 2006 11:30 pm Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| fjb_saper wrote: |
| jefflowrey wrote: |
It's probably what allows the queue manager to control the service once it's started.
I don't think it's actually a documented flag. |
I believe I saw it somewhere in the doc.
It is meant to register the listener with the qmgr...? |
I tested it (on Linux and Solaris) and found:
- Listeners defined and started via MQSC commands have the option -r in the process list.
- Listeners started via shell command runmqlsr -r ... cannot be seen via MQSC command dis lsstatus(*)
- Listeners started via shell command without option -r can be seen via MQSC command dis lsstatus(*)
So it is the other way round. Listeners started via shell command without option -r are named in dis lsstatus(*) command as
SYSTEM.LISTENER.TCP.no (no is a number).
I guess, the option -r suppresses the creation of such a system listener status.
_________________
Regards
Hubert |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 31, 2006 2:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think you missed a test case that would put the doubt back into your theory.
I think the -r has to do with allowing the parent process to control the service once it's started.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
