Circumstances where activity information is not acquired

To determine the complete sequence of activities performed on behalf of a message, information related to every activity must be acquired. If the information relating to any activity has not been recorded, or has not been acquired, then only a partial sequence of activities can be determined.

The following are circumstances where activity information is not recorded:

• The message is processed by a WebSphere MQ queue manager prior to V6.0.

• The message is processed by a queue manager that is not enabled for activity recording.

• The application expected to process the message is not running.

The following are circumstances where recorded activity information is unable to reach the specified reply-to queue:

• There is no channel defined to route activity reports to the reply-to queue.

• The channel to route activity reports to the reply-to queue is not running.

• The remote queue definition to route activity reports back to the queue manager where the reply-to queue resides (the queue manager alias), is not defined.

• The user that generated the original message does not have open, or put, authority to the queue manager alias.

• The user that generated the original message does not have open, or put, authority to the reply-to queue.

• The reply-to queue is put inhibited.

The following are circumstances where recorded activity information is unable to reach the system queue, or a common queue:

• If a common queue is to be used and there is no channel defined to route activity reports to the common queue.

• If a common queue is to be used and the channel to route activity reports to the common queue is not running.

• If a common queue is to be used and the system queue is incorrectly defined.

• The user that generated the original message does not have open, or put, authority to the system queue.

• The system queue is put inhibited.

• If a common queue is to be used and the user that generated the original message does not have open, or put, authority to the common queue.

• If a common queue is to be used and the common queue is put inhibited.

In these circumstances, providing the activity report does not have the report option MQRO_DISCARD_MSG specified, the activity report can be retrieved from a dead letter queue if one was defined on the queue manager where the activity report was rejected. An activity report will only have this report option specified if the original message, from which the activity report was generated, had both MQRO_PASS_DISCARD_AND_EXPIRY and MQRO_DISCARD_MSG specified in the Report field of the message descriptor.