Outbound messages - altering or specifying the transmission queue

Figure 15 shows a scenario where messages arrive at queue manager 'QM1' with transmission headers showing queue names at queue manager 'QM3'. In this scenario, 'QM3' is reachable by multi-hopping through 'QM2'.

Figure 15. Queue manager alias
The figure shows messages for QM3 arriving at QM1. The accompanying text explains the use of queue manager aliases, and the method for sending messages to their intended destination in this example.

All messages for 'QM3' are captured at 'QM1' with a queue manager alias. The queue manager alias is named 'QM3' and contains the definition 'QM3 via transmission queue QM2'. The definition looks like this:

DEFINE QREMOTE (QM3) RNAME() RQMNAME(QM3) XMITQ(QM2)

The queue manager puts the messages on transmission queue 'QM2' but does not make any alteration to the transmission queue header because the name of the destination queue manager, 'QM3', does not alter.

All messages arriving at 'QM1' and showing a transmission header containing a queue name at 'QM2' are also put on the 'QM2' transmission queue. In this way, messages with different destinations are collected onto a common transmission queue to an appropriate adjacent system, for onward transmission to their destinations.