IMS Transaction with the 2PC Protocol |IBM CICS Interface for Teradata References - An IMS Transaction with the 2PC Protocol: Example - IBM IMS Interface for Teradata

IBM IMS Interface for Teradata® Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
IBM IMS Interface for Teradata
Release Number
17.20
Published
November 2023
ft:locale
en-US
ft:lastEdition
2023-11-17
dita:mapPath
fks1695366180215.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
sjj1470436571402
Product Category
Teradata Tools and Utilities

With the 2PC protocol, a task is one invocation of an IMS transaction, and each task can update multiple database management systems (DBMSs).

The processing example in the following figure depicts such a task. The IMS task establishes sessions on the appropriate DBMSs and issues the updates.

A set of updates, such as Updates 1A, 1B, and 1C in the figure, will take the multiple databases from one state to another (in this case, from the initial state to State 1).

The set of updates is referred to as a logical unit of work. After each logical unit of work is completed, there is a “commit” or “rollback” action.

If a failure occurs so that a logical unit of work cannot be completed, the logical unit of work becomes a unit of recovery. The data can be recovered only back to the last completed logical unit of work.

An update within a Teradata session is occasionally referred to as a “transaction.”
2PC IMS Processing Example