About the Two-Phase Commit Protocol - Teradata Tools and Utilities

Teradata® Tools and Utilities for IBM z/OS Installation Guide

Product
Teradata Tools and Utilities
Release Number
16.20
Published
October 2018
Language
English (United States)
Last Update
2019-03-07
dita:mapPath
ovw1527114222335.ditamap
dita:ditavalPath
ovw1527114222335.ditaval
dita:id
B035-3128
lifecycle
previous
Product Category
Teradata Tools and Utilities

The Two-Phase Commit (2PC) protocol allows an application program to update databases on multiple database management systems, ensuring data consistency on all systems involved. If an application runs in Two-phase commit mode, all the changes in a defined logical unit of work either commit or roll back. In a system set up to support Two-phase commit transactions, there must be a coordinator (such as CICS or IMS) and one or more participants (such as the Teradata server or IBM DB2).

Two-phase commit is supported in Teradata Director Program Reference for UNIX Release 2.0 or higher. To set up your site to run applications that use Two-phase commit processing, you must customize the following:
  • TDPPARM file
  • IBM CICS Interface for Teradata (CICS Interface), for sites that use CICS as the coordinator. For details, see Installing CICS.
  • IBM IMS/DC Interface for Teradata (IMS/DC Interface), for sites that use IMS as the coordinator. For details, see Installing IMS/DC.
For additional background information on the Two-phase commit protocol, see the following manuals:
  • Teradata® Database Administration (B035-1093)
  • Teradata® Database Design, B035-1094