MQSeries.net :: View topic - CICS TRIGGER TRANS LOOPING

camvdcs · Posted: Fri Aug 15, 2008 7:29 am Post subject: CICS TRIGGER TRANS LOOPING - 2033

Environment: zOS 1.9, CICS TS 3.1, IBM WebSphere MQ for z/OS V6.

I had strange scenario occur in our test CICS environment. The CICS trigger transaction was in a loop early in the morning. The task would start and put up an MQGET only to get a 2033 return code. The program is coded to just RETURN TO CICS in this case. Well, it was looping so much that the time expired on the JOB and CICS went down. I looked at the MQ queue and it shows that there were 12 messages in the Current queue depth. I used a utility called 'MQUTIL' to browse the queue but it there were no messages. Somehow, the Current queue depth counter was incremented but the messages were not commited. Because MQ thought there were messages to be processed, it kept triggering the CICS Trans. I brought the CICS region back up and disabled the CICS trigger trans. Our testing unit came in an started working. They eventually performed a transaction that wrote an MQ message to the queue. We suddenly noticed that there were 13 messages now and we are able to browse and see all 13 messages. I enabled the CICS TRANS CODE and started the transaction and all messages cleared out and the Current queue depth returned to zero. Has anyone ever run into this scenario?

More info:

MQ message originates from a different MQ manager.

MQ Mgr A -----> MQ Mgr B ------> CICS
Channel transport = LU6.2
Trigger on FIRST
MQGET - no msgid specified, just get the message on the queue.