Enabling the CICS two-phase commit process

To enable CICS® to use a two-phase commit process to coordinate transactions that include MQI calls, add a CICS XAD resource definition stanza entry to the CICS region. Note, this topic is not applicable to z/OS®.

Here is an example of adding an XAD stanza entry for IBM MQ for Windows, where Drive is the drive where IBM MQ is installed (for example, D:).

cicsadd -cxad -rcics_region \
     ResourceDescription="MQM XA Product Description" \
     SwitchLoadFile="Drive:\Program Files\IBM\WebSphere MQ\bin\mqmc4swi.dll" \
     XAOpen=queue_manager_name

For extended transactional clients, use the switch load file mqcc4swi.dll. Here is an example of adding an XAD stanza entry for IBM MQ for UNIX and Linux systems, where MQ_INSTALLATION_PATH represents the high-level directory in which IBM MQ is installed:

cicsadd -cxad -rcics_region \
      ResourceDescription="MQM XA Product Description" \
      SwitchLoadFile="MQ_INSTALLATION_PATH/lib/amqzsc" \
      XAOpen=queue_manager_name

For extended transactional clients, use the switch load file amqczsc.

For information about using the cicsadd command, see the CICS Administration Reference, or CICS Administration Guide for your platform.

Calls to IBM MQ can be included in a CICS transaction, and the IBM MQ resources will be committed or rolled back as directed by CICS. This support is not available to client applications.

You must issue an MQCONN from your CICS transaction in order to access IBM MQ resources, followed by a corresponding MQDISC on exit.