Modifying PTCSYNCH values (MODIFY PTCSYNCH)

 MODIFY PTCSYNCH,
    VALUE=([{WAIT | ABORT | COMMIT}]          
           [,[{WAIT | ABORT | COMMIT}]])

For UDS-D/openUTM

The first value of the PP PTCSYNCH statement applies to secondary subtransactions or openUTM transactions that are in the PTC state at the time of a warm start.

For UDS-D

The second value of the PP PTCSYNCH statement applies to secondary subtransactions that are in the PTC state in the course of the current session and for which the state of the corresponding primary subtransaction cannot be ascertained.

WAIT	The secondary subtransactions/openUTM transactions wait until they are terminated either by a message from the corresponding primary subtransaction or openUTM or explicitly by the database administrator using the DAL command ABORT, OPTION=PTC or COMMIT.
ABORT
	UDS/SQL rolls back the secondary subtransactions/openUTM transactions (FINISH WITH CANCEL) and issues a warning to the database administrator.
COMMIT
	UDS/SQL terminates the secondary subtransactions/openUTM transactions, commits the updates (FINISH) and issues a warning to the database administrator.

The DAL command MODIFY PTCSYNCH is used to change the values of the DBH load parameter PP PTCSYNCH dynamically during the session. This makes it possible to terminate secondary subtransactions/openUTM transactions in the PTC condition. If one of the two values is left unspecified, the current value remains unchanged.

It may be necessary to change the default value (WAIT) for warm starts if the database administrator wishes to use a warm start to attach a database in which a secondary subtransaction or a openUTM transaction is in the PTC condition.
By changing the PTCSYNCH value from WAIT to COMMIT or ABORT, the database administrator causes enforced attachment of the database.

Interconfiguration consistency (or UDS/SQL openUTM consistency, as appropriate) is at risk if the PTCSYNCH value is not set to (WAIT,WAIT) (default value) (see section “Terminating the PTC state”).
Physical consistency within a configuration is assured regardless.