Distributed command times out
Look up the code X’7F1’, which is displayed by the EXEC in the BBI Journal.

According to IBM MQ Messages, X’7F1’ means a MQGET request timed out.
- We know the QAO is active because the EXEC used the MQI successfully.
- Since there are no Rules to consider, you do not need to refer to the Rules Processor Automation Control panels.
- Look at the BMC AMI Ops Automation for MQ OCD.
- The panel indicates that BMC AMI Ops Automation for MQ is connected to queue manager CSQ4, which is correct.There are no Rules, so you do not need to determine which queues are eligible for automation.
- Return to BMC AMI Ops Monitor for MQ to complete the following procedures:
- Validate the z/OS queue manager.
Obtain the name of the transmission queue.In this case, the queue manager alias is PCOCHRAN and its transmission queue is CSQ4.

Verify that the XMITQ is empty by hyperlinking from XMITQ to a detailed view.

Verify that the Sender channel is running by hyperlinking to the CHNLS view.

Verify that the Receiver Channel is running.

- Validate the distributed queue manager.In this example, we are using native IBM MQ commands on Windows.
Verify that the command queue is empty and enabled.
Stop the command server and reissue the command.The command is present in the queue.

- Restart the command server.
Determine if the queue manager alias is PUT inhibited.

- Alter the queue manager alias to PUT (ENABLED).The distributed command no longer times out.