Transactional support scenarios
Use transactional support we can enable the applications to work reliably with databases.
This section introduces transactional support. The work required to enable the applications to use IBM MQ with a database product spans the areas of application programming and system administration. Use the information here together with Committing and backing out units of work.
We start by introducing the units of work that form transactions, then describe the ways in which you enable IBM MQ to coordinate transactions with databases.
- Introducing units of work
This topic introduces and defines the general concepts of unit of work, commit, backout and sync point. It also contains two scenarios that illustrate global units of work.- Scenario 1: Queue manager performs the coordination
In scenario 1, the queue manager acts as the transaction manager. In this scenario, MQI verbs control the global units of work; they are started in applications using the MQBEGIN verb and then committed using MQCMIT or backed out using MQBACK.- Scenario 2: Other software provides the coordination
In scenario 2, an external transaction manager coordinates global units of work, starting and committing them under control of the transaction manager's API. The MQBEGIN, MQCMIT, and MQBACK verbs are unavailable.- Expiring global units of work
The queue manager can be configured to expire global units of work after a pre-configured interval of inactivity.- Unit of recovery disposition
IBM MQ for z/OS provides unit of recovery dispositions. This feature allows you to configure whether the second phase of 2-phase commit transactions can be driven, for example, during recovery, when connected to another queue manager within the same queue sharing group (QSG).Parent topic: IBM MQ Scenarios
Related concepts
Related information