UDS-D mode can be terminated by
terminating the DBH or
terminating only UDS-D mode.
Terminating the DBH
The DBH can be terminated with one of the following DAL commands:
CLOSE RUN-UNITS (normal DBH termination)
CLOSE CALLS (accelerated, but normal DBH termination using FINISH WITH CANCEL for all open transactions).
UDS/SQL can terminate the DBH with CLOSE RUN-UNITS or CLOSE CALLS only if none of the subtransactions are in the PTC state.
The database administrator can, however, force the DBH to terminate even if there are subtransactions in the PTC state (see section “Terminating the PTC state”).%TERM (instant DBH abort, without terminating open transactions)
Subtransactions in the PTC state remain in the same state and are subsequently handled in a warm start as defined by the value of the DBH load parameter PP PTCSYNCH (see “Effects of the PTC state during a warm start”).
The DAL commands to terminate the DBH are described in section “Terminating the DBH”.
Terminating UDS-D mode
UDS-D mode can be terminated with DAL command &CLOSE DISTRIBUTION. When all subtransactions have been closed, UDS/SQL terminates the UDS-D task UDSCT. Subtransactions in the PTC state that could not be terminated within a time interval defined by PP CHCKTIME remain in the PTC state. Once the UDS-D task has been terminated, UDS/SQL will accept neither the remote processing chains of a local application program, nor the secondary subtransactions of a remote application program.
If desired, the terminated UDS-D mode can also be restarted for the same session (see section “Restarting UDS-D mode”).