MQSeries.net :: View topic - dspmqrte

abarrett · Posted: Mon Apr 05, 2010 12:20 am Post subject: dspmqrte - unexpected behaviour

I have been using the dspmqrte utility (using MQV7) and requesting that a traceroute reply message is generated and forwarded to a particular reply queue.
eg dspmqrte -m LUPMB02 -q LU.QA.TRACEROUTE.MB2.REQUEST.GW -o -w 30 -xs -1 -rq LU.QL.TRACEROUTE.REPLY -ac -ar -ro discard -v summary
From my reading of the manual, i got the impression that a single traceroute reply would be generated and sent back to LU.QL.TRACEROUTE.REPLY, but I am seeing multiple replies being generated. The message path I have defined actually targets a remote queue which effectively echos the message back to the listed reply queue.
1) On QM1, Message put to cluster queue LU.QA.TRACEROUTE.MB2.REQUEST.GW hosted on gateway qmgr (QM2)
2) LU.QA.TRACEROUTE.MB2.REQUEST.GW on gateway (QM2) resolves to a clustered remote queue on another qmgr (QM3)
3) The remote queue points back to LU.QL.TRACEROUTE.REPLY on QM1 via QM2 (by utilising a qmgr alias name in the rqmname field)

The output from dspmqrte is correct ( captures the entire message path), however it seems that 3 traceroute replies are generated. 2 from MQgateway (QM2) (1 outbound, 1 inbound) and 1 from the target qmgr QM3. Although the command completes successfully, I am left with 1 'spare' message on the reply queue for each invocation of the utility. Does anyone understand why the utility and qmgrs would behave in this manner. I was expecting only 1 single reply message.