MQ

 View Only

 DLQ monitoring using activity trace?

John Hawkins's profile image
John Hawkins IBM Champion posted Fri August 01, 2025 12:50 PM

Hi all,

I suspect this is slightly obscure but...

I'm looking to use activity trace to track messages and I would like to add the DLQ into this tracking - rather than set up a separate mechanism just for the DLQ.

However, I have setup a scenario whereby a a remote QM sends a message to QM2 where there is no such queue i.e. it's the channel that's putting the message to the DLQ on QM2. And... I don't see the message in the activity trace. I had hoped to see, perhaps, the channel process in the activity trace. Am I missing it (there's a lot of trace!) or is there any magic incantation to get DLQ/mq processes activity traced.

As I say, I have fallback positions to monitor the DLQ - but I'd rather just use the activity trace if I can. So, any help would be appreciated.

many thanks - as always !

John.

Morag Hughson's profile image
Morag Hughson IBM Champion

I can confirm that the channel does show up in Activity Trace, here' some I generated just now:
- 09:05:22  34092(  2) [ 2832us] :\mqm9400\bin64\amqrmppa.exe MQCONNX 
- 09:05:22  34092(  2) [   62us] :\mqm9400\bin64\amqrmppa.exe MQOPEN NOT.EXIST RC(2085) Unknown object name
- 09:05:22  34092(  2) [   66us] :\mqm9400\bin64\amqrmppa.exe MQOPEN 
+ 09:05:22  34092(  2) [   17us] :\mqm9400\bin64\amqrmppa.exe MQINQ 
  Sat Aug  2 09:05:22 2025
  Context
  MQINQ(
     Connection Id:414D51434D5147322020202020202020FA2B8D6800280040
     Hobj         :4 QMGR(MQG2)
     Sel. Count   :1    
     Selectors    :[0]  2006 MQCA_DEAD_LETTER_Q_NAME
     CompCode     :0    
     Reason       :0     OK
    )
- 09:05:22  34092(  2) [   12us] :\mqm9400\bin64\amqrmppa.exe MQCLOSE 
- 09:05:22  34092(  2) [  504us] :\mqm9400\bin64\amqrmppa.exe MQOPEN SYSTEM.DEAD.LETTER.QUEUE 
- 09:05:22  34092(  2) [   73us] :\mqm9400\bin64\amqrmppa.exe MQPUT SYSTEM.DEAD.LETTER.QUEUE 
- 09:05:22  34092(  2) [  286us] :\mqm9400\bin64\amqrmppa.exe MQCMIT 

Perhaps you did not turn on activity trace until after the channel had started? I turned it on and then recycled my queue manager just to be certain. Long running applications, which I guess amqrmppa would count as, may not pick up the instruction to use activity trace if they are already running.

Cheers,
Morag