CLIv2 Application Requirements for Two-phase Commit - Call-Level Interface Version 2

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

Product
Call-Level Interface Version 2
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-07
dita:mapPath
jen1488824663137.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2417
lifecycle
previous
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).