Teradata Transaction-semantics - Teradata Tools and Utilities

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

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Tools and Utilities
Release Number
17.20
Published
June 2022
ft:locale
en-US
ft:lastEdition
2023-11-17
dita:mapPath
oxw1641281447623.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
vfj1470443597526
Product Category
Teradata Tools and Utilities

Two modes of transactions are available:

  • Teradata
  • ANSI

If Teradata Transaction-semantics are used, three types of transactions differ in the way an application identifies which statements share the all-or-none property. All three methods back out all statements if any statement fails:

  • Explicit (user-generated)- Precedes the statements by a BEGIN TRANSACTION statement and follows them with an END TRANSACTION statement.
  • Implicit - Submits the statements as a single request.
  • Two-phase commit - The action depends on CICS or IMS sync point services to commit or roll back transactions. The use of the sync point services guarantees that all updates performed within a logical unit of work will either all commit or all roll back.