Terminates a DBH session
Scope of validity
DBH administration
Function
The STOP-DBH statement terminates the DBH session.
Before the DBH session is terminated, the DBH rolls back all open transactions except PTC transactions, empties all buffers and closes the databases involved. If there are PTC transactions, utility statements or lock sequences in the system, SESAM/SQL rejects the statement. A table containing an overview of these PTC transactions or statements is output. The TA-LOG file remains active.
In the case of an application with SESAM/SQL and openUTM, the STOP-DBH statement allows you to choose whether the restart information for the UTM warm start is to be backed up or deleted.
The restart information is backed up by default. This is important when a DBH restart, but not a UTM warm start, has been carried out after a system failure. Only if the restart information of the DBH (TA-LOG and WA-LOG file) has been backed up is a UTM warm start possible in the following DBH session.
You can terminate the DBH up to 64 times with restart-information backup without endangering the UTM warm start.
STOP-DBH |
UTM-SESSION-INFO = *KEEP / *DELETE |
Operands
UTM-SESSION-INFO =
Specifies whether the restart information for the UTM warm start is to be backed up or deleted.
UTM-SESSION-INFO = *KEEP
This is the default. The restart information from the TA-LOG and WA-LOG files of the DBH is backed up in case a UTM warm start becomes necessary.
UTM-SESSION-INFO = *DELETE
The restart information for the UTM warm start is deleted.
Administration command in ISP format and at the CALL DML interface
Two administration commands fulfill the function of the STOP-DBH administration statement: STOP[,KEEP] and STOP,DELETE.
STOP[,KEEP]
STOP,DELETE
If you enter only STOP, SESAM/SQL uses the STOP,KEEP command internally.