Preparing channels and transmission queues for remote administration

How to use MQSC commands to prepare channels and transmission queues for remote administration.

To run MQSC commands remotely, set up two channels, one for each direction, and their associated transmission queues. This example assumes that you are using TCP/IP as the transport type and that you know the TCP/IP address involved.

The channel source.to.target is for sending MQSC commands from the source queue manager to the target queue manager. Its sender is at source.queue.manager and its receiver is at target.queue.manager. The channel target.to.source is for returning the output from commands and any operator messages that are generated to the source queue manager. You must also define a transmission queue for each channel. This queue is a local queue that is given the name of the receiving queue manager. The XMITQ name must match the remote queue manager name in order for remote administration to work, unless you are using a queue manager alias. Figure 1 summarizes this configuration.
Figure 1. Setting up channels and queues for remote administration
A diagram showing you how to set up channels and queues for remote administration. The channel source.to.target sends MQSC commands from the source queue manager (source.queue.manager) to the target queue manager (target.queue.manager). The channel target.to.source returns the output from commands and any operator messages that are generated to the source queue manager. You must also define a transmission queue for each channel. In the diagram, source.queue.manager contains an XMITQ definition of target.queue.manager; target.queue.manager contains an XMITQ definition of source.queue.manager.

See Configuring distributed queuing for more information about setting up channels.