Enabling Two-phase Commit Protocol - 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 CLIv2 application specifies whether it is using the Two-phase commit protocol at connect time. There is no limit to the number of sessions running in either mode, other than the maximum number allowed for the system.

To initiate the protocol for a session, the application can perform either of the following actions:

  • Set the Two-phase-commit DBCAREA option and execute a CLIv2 Connect function in the individual application.
  • Set Two-phase commit as the default for all applications through the HSHSPB.
To use this option as the default mode... Specify this setting in IBO2PC in the system parameter block (HSHSPB)...
Two-phase commit Y
non-Two-phase commit N

If any value is set for the Two-phase-commit DBCAREA option, the HSHSPB protocol setting is ignored.