If your application uses distributed queuing, consider the following points:
DISPLAY QUEUE (qname) IPPROCS
If the value for IPPROCS is 0, this means that the channel serving this transmission queue is not running.
DISPLAY CHSTATUS (channel-name) STATUS MSGS
Use the output produced by this command to check that the channel is serving the correct transmission queue and that it is connected to the correct target machine and port. You can determine whether the channel is running from the STATUS field. You can also see if any messages have been sent on the channel by examining the MSGS field.
If the channel is in RETRYING state, this is probably caused by a problem at the other end. Check that the channel initiator and listener have been started, and that the channel has not been stopped. If somebody has stopped the channel, you need to start it manually.
This could mean that an application could not put the required message on to the queue. If this is so, check if the message has been put on to the dead-letter queue.
The dead-letter queue message header (dead-letter header structure) contains a reason or feedback code explaining why the message could not be put on to the target queue. See the WebSphere MQ Application Programming Reference manual for information about the dead-letter header structure.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq424d |