Home

 

Problems with incorrect output when using distributed queues

 

If your application uses distributed queues, consider the following points:

• Has WebSphere MQ been correctly installed on both the sending and receiving systems, and correctly configured for distributed queuing?

• Are the links available between the two systems?

  Check that both systems are available, and connected to WebSphere MQ. Check that the connection between the two systems is active.

  We can use the MQSC command PING against either the queue manager (PING QMGR) or the channel (PING CHANNEL) to verify that the link is operable.

• Is triggering set on in the sending system?

• Is the message for which you are waiting a reply message from a remote system?

  Check that triggering is activated in the remote system.

• Is the queue already full?

  If so, check if the message has been put onto the dead-letter queue.

  The dead-letter queue header contains a reason or feedback code explaining why the message could not be put onto the target queue. See the Application Programming Reference for information about the dead-letter queue header structure.

• Is there a mismatch between the sending and receiving queue managers?

  For example, the message length could be longer than the receiving queue manager can handle.

• Are the channel definitions of the sending and receiving channels compatible?

  For example, a mismatch in sequence number wrap can stop the distributed queuing component. See WebSphere MQ Intercommunications for more information about distributed queuing.

• Is data conversion involved? If the data formats between the sending and receiving applications differ, data conversion is necessary. Automatic conversion occurs when the MQGET call is issued if the format is recognized as one of the built-in formats.

  If the data format is not recognized for conversion, the data conversion exit is taken to allow you to perform the translation with your own routines.

  Refer to the WebSphere MQ Application Programming Guide for further details of data conversion.

 

Parent topic:

Have you obtained incorrect output?

fa15020_

 

Home