Secondary subtransactions in the PTC state wait for the FINISH or FINISH WITH CANCEL statement from the associated primary subtransaction.
If a secondary subtransaction loses the logical connection to its primary subtransaction in this phase, the automatic PTC monitoring performed by UDS-D becomes critically important.
A secondary subtransaction in the PTC state waits for a message from the primary subtransaction for a defined time interval, which depends on PP CHCKTIME. Following this interval, the UDS-D task of the secondary subtransaction automatically tries to determine the state of the associated primary subtransaction. If this is successful, the secondary subtransaction is handled in the same way as the primary subtransaction. If the attempt fails, the secondary subtransaction is handled as determined by the value of the DBH load parameter PTCSYNCH for the current session, i.e. if PTCSYNCH is set to ABORT or COMMIT, the secondary subtransaction in the PTC state is terminated with ABORT or COMMIT, and if PTCSYNCH is set to WAIT, it remains in the PTC state.
If desired, the DAL command &SYNCHRONIZE DISTRIBUTION can be used by the database administrator to speed up the process of checking the configuration of the primary subtransaction. If the configuration of the primary subtransaction cannot be reached even after &SYNCHRONIZE DISTRIBUTION, all secondary subtransactions for which the state of the primary subtransaction cannot be determined are handled as set in the PTCSYNCH value for the current session on completion of the &SYNCHRONIZE DISTRIBUTION command.