CLIv2 Application Requirements for Two-phase Commit - Teradata Tools and Utilities

Teradata® Call-Level Interface Version 2 Reference for Mainframe-Attached Systems - 20.00

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Lake
Product
Teradata Tools and Utilities
Release Number
20.00
Publication Date
October 2023
Content Type
Programming Reference
Publication ID
B035-2417-103K
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
apo1695647516691.ditamap
dita:ditavalPath
obe1474387269547.ditaval
ft:sourceId
dita
dita:id
vfj1470443597526
Product Category
Teradata Tools and Utilities

The following requirements apply to CLIv2 applications that use the Two-phase commit protocol:

  • The application must establish a Two-phase commit session, initiate requests, and use the coordinator‘s sync point facilities to commit the updates rather than issue direct commands to the participant.
  • Any connection used for Two-phase commit requests must be specified as a Two-phase commit connection.

    For example, you can use the Two-phase-commit DBCAREA option or set the Two-phase commit default in the HSHSPB.

  • An END TRANSACTION statement must have a corresponding BEGIN TRANSACTION preceding it. For applications in Two-phase commit mode, both of these commands can be used only in inner nested transactions.
  • The application must use CICS/VS or IMS/VS syncpoint processing to commit or abort the transaction (not END TRANSACTION, ROLLBACK WORK, COMMIT WORK, or ABORT).