Example 1 - Requesting activity reports

In this example the WebSphere MQ display route application connects to queue manager, QM1, and is used to generate and deliver a trace-route message to the target queue, TARGET.Q, on remote queue manager, QM2. The necessary report option is specified so that activity reports are requested as the trace-route reply message is routed. On arrival at the target queue the trace-route message is discarded. Activity information returned to the WebSphere MQ display route application using activity reports is put in order and displayed.

Figure 11. Requesting activity reports, Diagram 1
 Illustration showing:  Two queue managers QM1 and QM2, connected by two channels (QM2.TO.QM1 and QM1.TO.QM2). An activity report being placed by DSPMQRTE in local queue ACTIV.REPLY.Q of QM1. A trace route message being placed by DSPMQRTE in remote queue TARG.AT.QM2 of QM1.

Figure 12. Requesting activity reports, Diagram 2
 Illustration showing:  Two queue managers QM1 and QM2, connected by two channels (QM2.TO.QM1 and QM1.TO.QM2). An activity report being passed from the transmission queue QM2 through the MCA to local queue ACTIV.REPLY.Q of QM1.

Figure 13. Requesting activity reports, Diagram 3
 Illustration showing:  Two queue managers QM1 and QM2, connected by two channels (QM2.TO.QM1 and QM1.TO.QM2). An activity report being passed from the MCA through remote queue QM1 in queue manager QM2 and added to the queue ACTIV.REPLY.Q of QM1. A trace route message received from QM1 being discarded.

Figure 14. Requesting activity reports, Diagram 4
 Illustration showing :  Two queue managers QM1 and QM2, connected by two channels (QM2.TO.QM1 and QM1.TO.QM2). DSPMQRTE removing activity reports from the local queue ACTIV.REPLY.Q of QM1.