This statement commits a PTC transaction.
Scope of validity
DBH administration
See also
The ROLLBACK-PTC-TRANSACTION administration statement on "ROLLBACK-PTC-TRANSACTION"
Function
The COMMIT-PTC-TRANSACTION statement commits a user's PTC transactions. A PTC transaction is a distributed transaction that has the status “prepared to commit” (see the “ Core manual”).
openUTM-D and SESAM/SQL-DCN permit distributed transactions involving several DBHs. Distributed or PTC transactions are divided into three phases:
the processing of the transaction
the prepare-to-commit phase
the commitment (completion) of the transaction
In an external restart of the SESAM/SQL DBH, the transaction and restart mechanism of openUTM-D or SESAM/SQL-DCN controls the final commitment and, if appropriate, rolling back of PTC transactions.
If a restart through openUTM-D or SESAM/SQL-DCN is not possible because, for example, the computers involved are no longer accessible, the system administrator can use the COMMIT-PTC-TRANSACTION administration statement to complete and thus commit a user's PTC transactions in the node for which he or she is responsible.
This statement is only relevant to PTC transactions. If no PTC transactions are active in the DBH, the statement is rejected. It is also rejected if the DBH was loaded without transaction management.
If a user does not have any transaction in the PTC status, then a message is output.
COMMIT-PTC-TRANSACTION |
USER = <user-identification> |
Operands
USER = <user-identification>
Identifies the user whose PTC transactions are to be completed. The identification must be unique. You must specify all the relevant partial qualifications (see section “Syntax for the identification of users”).
Administration command in ISP format and at the CALL DML interface
The CPTC administration command corresponds to the COMMIT-PTC-TRANSACTION administration statement here.
CPTC,user-identification