Is the channel moving messages?
Having issued the command
DIS CHSTATUS(QM1.TO.QM2) ALL, if the output shows the status of the channel is
RUNNING, then it has successfully connected to the partner system.
Providing there are no uncommitted messages on the transmission queue, see Are the messages on the queue available?, then there are messages available for the channel to get and send. Do the following:
- In the output from the display channel status command,
DIS CHSTATUS(QM1.TO.QM2) ALL, look at the following fields:
Determine whether the channel has sent any messages since it started. If any have been sent, determine when the last message was sent.
- MSGS
- Number of messages sent or received (or, for server-connection channels, the number of MQI calls handled) during this session (since the channel was started).
- BUFSSENT
- Number of transmission buffers sent. This includes transmissions to send control information only.
- BYTSSENT
- Number of bytes sent during this session (since the channel was started). This includes control information sent by the message channel agent.
- LSTMSGDA
- Date when the last message was sent or MQI call was handled, see LSTMSGTI.
- LSTMSGTI
- Time when the last message was sent or MQI call was handled. For a sender or server, this is the time the last message (the last part of it if it was split) was sent. For a requester or receiver, it is the time the last message was put to its target queue. For a server-connection channel, it is the time when the last MQI call completed.
- CURMSGS
- For a sending channel, this is the number of messages that have been sent in the current batch. For a receiving channel, it is the number of messages that have been received in the current batch. The value is reset to zero, for both sending and receiving channels, when the batch is committed.
- If the channel has started a batch, which has not yet completed (indicated by a non-zero value in CURMSGS), it could be waiting for the other end of the channel to acknowledge the batch. Look at the SUBSTATE field in the output and refer to Table 26:
Table 26. Sender and receiver MCA substates Sender SUBSTATE Receiver SUBSTATE Notes MQGET RECEIVE Normal states of a channel at rest. SEND RECEIVE SEND is usually a transitory state. If SEND is seen it indicates that the communication protocol buffers have filled. This can indicate a network problem. RECEIVE If the sender is seen in RECEIVE substate for any length of time, it is waiting on a response, either to a batch completion or a heartbeat. See Does a batch take a long time to complete? for more details.