| Author |
Message
|
| jeevan |
 Posted: Wed Mar 26, 2008 3:36 pm Post subject: Issuing MQSC commands on a remote queue manager |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
I am not sure whether I understood the meaning of this feature but what I need is to issue an MQSC command to remote queue manager.
I tried psexec which does not like echo format of the command. It runs if I issue runmqsc QMGR but does not work echo command |runmqsc QMGR
I then turned toward the MQseries feature
Issuing MQSC commands on a remote queue manager
I followed the given in the inforceter help page which is I have paste down.
runmqsc -w 30 target.queue.manager
it did not work.
I have issued this command staying in a server where mq is installed.
I did not understand only with this how mq goes and find this queue manager. The doc does not say anything. Do I need to set up some variable?
any help would be appreciated.
thanks a lot
[qoute]
The command server must be running on the target queue manager, if it is going to process MQSC commands remotely. (This is not necessary on the source queue manager). For information on how to start the command server on a queue manager, see Starting the command server.
On the source queue manager, you can then run MQSC commands interactively in indirect mode by typing:
runmqsc -w 30 target.queue.managerThis form of the runmqsc command, with the -w flag, runs the MQSC commands in indirect mode, where commands are put (in a modified form) on the command server input queue and executed in order.
When you type in an MQSC command, it is redirected to the remote queue manager, in this case, target.queue.manager. The timeout is set to 30 seconds; if a reply is not received within 30 seconds, the following message is generated on the local (source) queue manager:
AMQ8416: MQSC timed out waiting for a response from the command server.When you stop issuing MQSC commands, the local queue manager displays any timed-out responses that have arrived and discards any further responses.
In indirect mode, you can also run an MQSC command file on a remote queue manager. For example:
runmqsc -w 60 target.queue.manager < mycomds.in > report.outwhere mycomds.in is a file containing MQSC commands and report
[/qoute][/quote] |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Mar 26, 2008 4:34 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
runmqsc will try to find a "default route" from the default local queue manager to the remote queue manager, when you ask it to talk to a remote queue manager.
This usually means "An XMITQ with the same name".
You could look at MS0S for all your "remote" MQSC command needs...
Perhaps I'm biased.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Mar 26, 2008 11:13 pm Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
The instructions for the objects to define are in the Info Centre topic 'Preparing channels and transmission queues for remote administration'.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Mar 27, 2008 7:40 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
Jeff/Nigel,
I have missed a portion of it which I got now. Probably, I can not implement as the queue manaqger I want to issue command remotely is a production qmgr. I need to do that to reset cluster ( remove one queue manager which we are taking apart in order to upgrade it. I thought whether I can do this staying in the box the queue manager to be upgraded resides. However, it is not a big issue or anything. I can go to FR queue manager and do it. I just wanted to see this feature but I understand now what it requies. It seeems it doese not work in cluster and requires explicit xmitq and channel to the target queue manager.
Thanks for your replies though.
| Nigelg wrote: |
| The instructions for the objects to define are in the Info Centre topic 'Preparing channels and transmission queues for remote administration'. |
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 27, 2008 7:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It should work in a cluster.
Unless the admins have sensibly taken steps to prevent it from happening in production.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Mar 27, 2008 9:14 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
And it only works if you have a "default" Queue Manager, because that's the one that runmqsc connects to.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| jeevan |
| Posted: Thu Mar 27, 2008 9:17 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| EddieA wrote: |
And it only works if you have a "default" Queue Manager, because that's the one that runmqsc connects to.
Cheers, |
This explains why it does not work. The queue manager is not set as default.
Thanks all |
|
| Back to top |
|
|
|
|
