CICS-MQ transaction tracking support

CICS® transaction tracking support includes tasks that are initiated by both IBM® MQ trigger and bridge monitors.

CICS adapter tracking support includes tasks that are initiated by IBM MQ trigger or bridge monitors.

IBM MQ trigger or bridge monitor tasks are supported by CICS transaction tracking by setting adapter fields in the origin data of the task that they start within a CICS region. The following adapter fields are intended to be used in hierarchical order. The adapter identifier specifies the general information, and the adapter data 3 specifies the most specific information. This method provides a uniform manner to identify and isolate tasks.
  1. Originating Adapter ID

    The product identifier for the version of IBM MQ queue that is being used. For example, ID=IBM WebSphere® MQ for z/OS® V7.0.1

  2. Originating Adapter Data 1

    The name of the IBM MQ queue manager. For example, QMGR=RQ38.

  3. Originating Adapter Data 2

    The name of the initiation queue from which a trigger monitor retrieved the trigger message and started this task. For example, INITQ=ALIINIT1.

    The name of the initiation queue is not applicable for the CICS-MQ Bridge scenario, so Adapter Data 2 sets to the default value. For example, INITQ=Not Applicable.

  4. Originating Adapter Data 3

    The name of the application message queue on which a message is put, as a result the task is started. For example, QNAME=ALITRIG1.

For remote transactions, the adapter data that applies to the mirror transaction when it is first attached is used for all subsequent START commands that use that mirror, regardless of what is set on their individual START commands.