In some cases, it may not be possible to terminate transactions in the PTC state, e.g. due to a failure in a partner system or transmission line. If the problem cannot be solved within an acceptable period, UDS-D offers the database administrator a facility to intervene in order to resume database operation. He or she can
use the DBH load parameter PP PTCSYNCH to control whether secondary subtransactions or openUTM transactions in the PTC state should terminate with FINISH or with
FINISH WITH CANCEL after a time interval defined by PP CHCKTIME. The value of the DBH load parameter PP PTCSYNCH can also be modified by the database administrator during a session by means of the DAL command MODIFY.use the DAL commands ABORT,OPTION=PTC or COMMIT to terminate secondary subtransactions or openUTM transactions with FINISH or with FINISH WITH CANCEL “manually”.
When the PTC state is terminated by the database administrator, crossconfiguration consistency or the UDS/SQL and openUTM consistency will no longer be guaranteed as soon as
the DBH load parameter PP PTCSYNCH is not set to (WAIT,WAIT) or
the database administrator intervenes with the DAL command ABORT,OPTION=PTC or COMMIT.
When secondary subtransactions or openUTM transactions in the PTC state are terminated by the database administrator, updates of the same transaction may be completed in the databases of one DB configuration, but not in those of another.
UDS/SQL informs the database administrator how the transaction is distributed so that he or she can take steps to limit or eliminate the inconsistency.
The consistency within a DB configuration is maintained in any case.