Which MQ Queue is related with which CICS transaction?

Which MQ Queue is related with which CICS transaction?

When a message is put on the MQ Queue, depending on the Q name, it automatically triggers the CICS transaction. But how do I know which MQ Queue is co-related with which CICS Transaction? Is there a way I can see the relation between the CICS Transaction and the Q name?
Thanks.

    Requires Free Membership to View

    Login

    When you register, you’ll also receive targeted alerts from my team of editorial writers and independent industry experts with the latest news, tips, and advice to help you do your job more efficiently and effectively. Our goal is to keep you informed on the hottest topics and biggest challenges faced by IT professionals today working with data center technologies.

    Margie Semilof, Editorial Director

    By submitting your registration information to SearchDataCenter.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDataCenter.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I assume you're talking about transactions started through the MQ trigger (CKTI) interface.

Probably the simplest thing to do is talk to the programmer in charge of the process that writes the messages. I believe the CICS transaction to be started is specified somewhere in the sending program.

If that's not available, you might be able to tell by looking at the handshake between the trigger initiator transaction (CKTI) and the target CICS transaction. When CKTI kicks off the application transaction it creates a message including the queue name the target task is supposed to read. You may be able to intercept that message using a debugging tool like CEDX or forcing an ABEND that would create a dump.

This was first published in January 2008

Back to top