MQ

 View Only

 Successful MQXF_CMIT followed by successful MQXF_BACK

Jump to  Best Answer
John Hawkins's profile image
John Hawkins IBM Champion posted Tue July 15, 2025 11:31 AM

Hi Folks,

related to my other question about activity trace. Why am I seeing this pattern on the same application thread?

MQIACF_OPERATION_ID:MQXF_CMIT

MQIACF_THREAD_ID:18

MQCACF_OPERATION_DATE:2025-07-15

MQCACF_OPERATION_TIME:14:49:27

MQIAMO64_QMGR_OP_DURATION:20

MQIACF_COMP_CODE:0

MQIACF_REASON_CODE:0

followed by

MQIACF_OPERATION_ID:MQXF_BACK

MQIACF_THREAD_ID:18

MQCACF_OPERATION_DATE:2025-07-15

MQCACF_OPERATION_TIME:14:49:28

MQIAMO64_QMGR_OP_DURATION:20

MQIACF_COMP_CODE:0

MQIACF_REASON_CODE:0

It seems to be telling me that the queue activities have been committed successfully (completion code is good) but then it's backing it out (with another good completion code).

In what state are the messages in that tran now - did they get committed OK or did they get backed out OK?

I'm confused - anyone know how to decipher this ?

thanks again !

Morag Hughson's profile image
Morag Hughson IBM Champion posted Tue July 15, 2025 10:54 PM  Best Answer

Ah here it is!

No problems with this. The MQCMIT was successful so the transaction is committed successfully. The MQBACK is a no-op.

I suspect, although you don't show it, that the MQBACK was directly before the MQDISC. Common practice. What kind of application is it?

Cheers,
Morag

John Hawkins's profile image
John Hawkins IBM Champion posted Wed July 16, 2025 05:42 AM

Thanks Morag !

Yes, the disconnect happened straight after which gave me a hint that it might just be a tidy-up but wasn't sure and it didn't happen for an amqsput/get that I started my tracing adventure with.

It's IBM ACE doing the connections. I think that's the C connector or do they switch to Java ?

(and thanks for the other thread too - I had even read that presentation but hadn't concentrated enough on that section to recognise it was important for me - doh !)

cheers !

Related Content