If your application uses distributed queues, consider the following points:
Check that both systems are available, and connected to WebSphere MQ for iSeries. Check that the connection between the two systems is active.
Check that triggering is activated in the remote system.
This could mean that an application was unable to put the required message on to the queue. If this is so, check if the message has been put onto the undelivered-message 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 or the WebSphere MQ for iSeries Application Programming Reference (ILE RPG), as appropriate, for information about the dead-letter header structure.
For example, the message length could be longer than the receiving queue manager can handle.
For example, a mismatch in sequence number wrap stops the distributed queuing component. See WebSphere MQ Intercommunication for more information about distributed queuing.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csq424d |