Home

 

Issuing MQSC commands on a remote queue manager

 

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, we can then run MQSC commands interactively in indirect mode by typing:

runmqsc -w 30 target.queue.manager

This 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, we can also run an MQSC command file on a remote queue manager. For example:

runmqsc -w 60 target.queue.manager < mycomds.in > report.out

where mycomds.in is a file containing MQSC commands and report.out is the report file.

• Working with queue managers on z/OS
  

 

Parent topic:

Remote administration from a local queue manager

fa11760_

 

Home