Does the problem affect only remote or cluster queues?

Use this topic for further investigation if the problem only occurs on remote or cluster queues.

Are the remote queues being accessed?

Check that the programs putting messages to the remote queues have run successfully (see Dealing with incorrect output on z/OS ).

Is the system link active?

Use APPC or TCP/IP commands as appropriate to check whether the link between the two systems is active.

Use PING or OPING for TCP/IP or D NET ID=xxxxx, E for APPC.

Is triggering working?

If we use triggering to start the distributed queuing process, check that the transmission queue has triggering set on and that the queue is get-enabled.

Is the channel or listener running?

If necessary, start the channel or the listener manually, or try stopping and restarting the channel. See Configure distributed queuing for more information.

Look for error messages on the startup of the channel initiator and listener. See IBM MQ for z/OS messages, completion, and reason codes and Configure distributed queuing to determine the cause.

What is the channel status?

Check the channel status using the DISPLAY CHSTATUS (channel_name) command.

Are your process and channel definitions correct?

Check your process definitions and your channel definitions.

See Configure distributed queuing for information about how to use distributed queuing, and for information about how to define channels. Parent topic: Is there a problem with the IBM MQ queues?