| Author |
Message
|
| reeturaj_sunny |
 Posted: Thu Aug 03, 2006 10:59 pm Post subject: Remote Administration from a local queue manager |
 |
|
Newbie
Joined: 26 Jun 2006
Posts: 9
Location: Mumbai,India
|
Hi all,
I am trying to do remote administration from local queue manager.
Both the queue managers are in windows platform.
As per the guidelines I have
1.Created channels
2.Started listeners.
3.Started command server on remote queue manager.
Now I am trying to issue MQSC commands from my source queue manager that will be executed in the remote queue manager.
runmqsc -w 30 <target.queue.manager>
But it's showing...
"WebSphere MQ queue manager not available"
Pls help..... |
|
| Back to top |
|
 |
| kevin_22 |
| Posted: Thu Aug 03, 2006 11:51 pm Post subject: |
|
|
Centurion
Joined: 08 Mar 2005
Posts: 100
|
It seems that you can apply this command only thru input and out files....
eg:
runmqsc -w 100 < input.in > output.out
**************
input.in
--------------
display
You will find the output file containing...
**************
output.out
--------------
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Starting MQSC for queue manager WBI6.0_QM.
1 : display
AMQ8405: Syntax error detected at or near end of command segment below:-
display
AMQ8426: Valid MQSC commands are:
DISPLAY AUTHINFO
DISPLAY CHANNEL
DISPLAY CHSTATUS
DISPLAY CLUSQMGR
DISPLAY PROCESS
DISPLAY NAMELIST
DISPLAY QALIAS
DISPLAY QCLUSTER
DISPLAY QLOCAL
DISPLAY QMGR
DISPLAY QMODEL
DISPLAY QREMOTE
DISPLAY QUEUE
DISPLAY QSTATUS
DISPLAY CONN
DISPLAY SERVICE
DISPLAY LISTENER
DISPLAY SVSTATUS
DISPLAY LSSTATUS
DISPLAY QMSTATUS
One MQSC command read.
1 command responses received.
Let me know any more issues...
Thanks,
Kevin |
|
| Back to top |
|
|
| reeturaj_sunny |
| Posted: Fri Aug 04, 2006 12:58 am Post subject: |
|
|
Newbie
Joined: 26 Jun 2006
Posts: 9
Location: Mumbai,India
|
| kevin_22 wrote: |
It seems that you can apply this command only thru input and out files....
eg:
runmqsc -w 100 < input.in > output.out
**************
input.in
--------------
display
You will find the output file containing...
**************
output.out
--------------
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Starting MQSC for queue manager WBI6.0_QM.
1 : display
AMQ8405: Syntax error detected at or near end of command segment below:-
display
AMQ8426: Valid MQSC commands are:
DISPLAY AUTHINFO
DISPLAY CHANNEL
DISPLAY CHSTATUS
DISPLAY CLUSQMGR
DISPLAY PROCESS
DISPLAY NAMELIST
DISPLAY QALIAS
DISPLAY QCLUSTER
DISPLAY QLOCAL
DISPLAY QMGR
DISPLAY QMODEL
DISPLAY QREMOTE
DISPLAY QUEUE
DISPLAY QSTATUS
DISPLAY CONN
DISPLAY SERVICE
DISPLAY LISTENER
DISPLAY SVSTATUS
DISPLAY LSSTATUS
DISPLAY QMSTATUS
One MQSC command read.
1 command responses received.
Let me know any more issues...
Thanks,
Kevin |
Hi,
I have tried with this...
runmqsc -w 30 target.queue.manager<input.in
But still gave
WebSphere MQ queue manager not available |
|
| Back to top |
|
|
| sebastianhirt |
| Posted: Fri Aug 04, 2006 1:04 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
Hi,
| Quote: |
| It seems that you can apply this command only thru input and out files.... |
This is not true. One can also run runmqsc interactive.
| Quote: |
-w WaitTime
Run the MQSC commands on another queue manager. You must have the required channel and transmission queues set up for this. See Preparing channels and transmission queues for remote administration for more information.
WaitTime
The time, in seconds, that runmqsc waits for replies. Any replies received after this are discarded, but the MQSC commands still run. Specify a time between 1 and 999 999 seconds.
Each command is sent as an Escape PCF to the command queue (SYSTEM.ADMIN.COMMAND.QUEUE) of the target queue manager.
The replies are received on queue SYSTEM.MQSC.REPLY.QUEUE and the outcome is added to the report. This can be defined as either a local queue or a model queue.
Indirect mode operation is performed through the default queue manager.
|
As you see in the snippet from the manual above, interactive connections to a queue manager can only be run via the default queue manager. So please make sure that you have set a default queue manager from the system you are running this command. Please make also sure that the default queue manager has the required connections to the remote queue manager.
Please check the manual for more information. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Aug 04, 2006 2:35 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And remember what you need as communications to the target qmgr is a default path back and forth. Read the intercommunications manual. The most clear explanation is in the multihopping part.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jpeela |
| Posted: Fri Aug 04, 2006 7:09 am Post subject: |
|
|
Centurion
Joined: 23 Jan 2006
Posts: 139
|
hi sunny,
sunny wrote
| Quote: |
As per the guidelines I have
1.Created channels
2.Started listeners.
3.Started command server on remote queue manager.
Now I am trying to issue MQSC commands from my source queue manager that will be executed in the remote queue manager.
runmqsc -w 30 <target.queue.manager>
But it's showing...
"WebSphere MQ queue manager not available" |
But did you create the channels and evry thing with the default queue manager.
I doubt it doesnt workout with other qmanagers other than default one.
_________________
Jogi |
|
| Back to top |
|
|
|
|
