Home

 

If you have problems using MQSC commands remotely

 

If you have difficulty in running MQSC commands remotely, make sure that you have:

• Started the command server on the target queue manager.

• Defined a valid transmission queue.

• Defined the two ends of the message channels for both:

  • The channel along which the commands are being sent.

  • The channel along which the replies are to be returned.

• Specified the correct connection name (CONNAME) in the channel definition.

• Started the listeners before you started the message channels.

• Checked that the disconnect interval has not expired, for example, if a channel started but then shut down after some time. This is especially important if you start the channels manually.

• Sent requests from a source queue manager that do not make sense to the target queue manager (for example, requests that include parameters that are not supported on the remote queue manager).

See also Resolving problems with MQSC commands.

 

Parent topic:

Remote administration from a local queue manager

fa11790_

 

Home