Rolling back one or all transactions (ABORT)

ABORT {transaction-id[,OPTION=PTC] | ALL}

Default value:
	without OPTION=PTC
transaction-id
	Identifies an open transaction which is to be rolled back.
OPTION=PTC
	Rolls back the specified transaction even if it is in the PTC state (only for UDS-D/openUTM).
ALL	Rolls back all currently open transactions except for those in the PTC condition.

The ABORT command rolls back the specified transaction or all currently open transactions. The COBOL(/CALL) DML application program involved receives the status code "122". SQL programs receive a status code < -1000 (SQL code).

The DBH accepts an ABORT command only for transactions that can be rolled back without any loss of data consistency.

Without the OPTION=PTC suffix, ABORT is ignored if the transaction is in the PTC condition.

With the OPTION=PTC suffix, the database administrator rolls back a secondary subtransaction or openUTM transaction "manually", even if it is in the PTC condition and is thus waiting for a termination message from the corresponding primary subtransaction or openUTM respectively.

The effect of the DBH load parameter PP PTCSYNCH is canceled for this transaction.

If it is not possible to roll back a transaction, e.g. because the RLOG file is incorrect or incomplete, the ABORT command is ignored by the DBH.

Rolling back a secondary subtransaction or a openUTM transaction in the PTC condition places the interconfiguration consistency or the UDS/SQL openUTM consistency at risk (see section “Terminating the PTC state”).