| Author |
Message
|
| KIT_INC |
 Posted: Thu Sep 21, 2006 3:20 pm Post subject: remote runmqsc without a default Qmgr |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
I know that I have to specify the Qmgr name on runmqsc if I do not have a default Qmgr
For example runmqsc MyQm
What if I have a few local Qmgr (but no default) and want to send mqsc command to a remote Qmgr
If I do
runmqsc -w 30 MyRemoteQm
which local Qmgr is sending the command to the remote Qmgr ? |
|
| Back to top |
|
 |
| wschutz |
| Posted: Thu Sep 21, 2006 3:43 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
The default qmgr ....
also, see supportpac MO72, which is a "client" version of runmqsc (actually called mqsc, but perhaps Paul should have called it runmqscc)....
_________________
-wayne
Last edited by wschutz on Thu Sep 21, 2006 3:48 pm; edited 1 time in total |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 21, 2006 3:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wschutz wrote: |
The default qmgr ....
also, see supportpac MO02, which is a "client" version of runmqsc (actually called mqsc, but perhaps Paul should have called it runmqscc).... |
Wayne I thought it was MO72 ?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Sep 21, 2006 3:48 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Yikes...someone swapped the 0 and the 7 on my keyboard.... I'll fix 
_________________
-wayne |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Thu Sep 21, 2006 7:07 pm Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
Thanks for all the replies.
Hi wschutz, I have 3 qmgrs on the system, but I did not specify any one of them as the default.
If I just enter
runmqsc -w 30 MyRemoteQm
I'll get AMQ8146: WebSphere MQ queue manager not available.
This may be a restriction of the runmqsc. I just want to make sure I did not miss any parameter on starting the runmqsc or if there is any undocumented parm which will allow me to specify the local Qmgr. |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Fri Sep 22, 2006 1:33 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
KIT_INC,
when you use runmqsc for remote administration, it connects always to the default QMgr. So you must have a default QMgr, otherwise runmqsc does not know, where connect to. This is described in the System Administration Guide.
Regards
Hubert
_________________
Regards
Hubert |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Sep 22, 2006 5:19 am Post subject: |
|
|
Guest
|
| runmqsc in indirect mode (runmqsc -w 30 MyRemoteQm) also requires that a sender-receiver pair exist between the local qmgr (that runmqsc connects to) and remote qmgr (that you want to admin), and that the sender channel's xmit queue (in your example) have the name MyRemoteQm. |
|
| Back to top |
|
|
|
|
