This statement terminates the lock sequence of another user.
Scope of validity
DBH administration
See also
DBH administration statement BEGIN-LOCK-SEQUENCE on "BEGIN-LOCK-SEQUENCE"
DBH administration statement END-LOCK-SEQUENCE on "END-LOCK-SEQUENCE"
Function
The ABORT-LOCK-SEQUENCE statement terminates a lock sequence that is uniquely identified by specifying the identification of the user.
All locks requested on databases and spaces during the lock sequence are released when the lock sequence is terminated.
The system administrator can protect himself or herself against the termination of his or her lock sequence by changing the password or administration authorization. The administrator can make these changes by using the DBH option ADMINISTRATOR or the DBH administration statement MODIFY-ADMINISTRATION (see "ADMINISTRATOR" or "MODIFY-ADMINISTRATION").
You must observe the following points when using the ABORT-LOCK-SEQUENCE statement:
The administration statement is rejected if the SESAM DBH was loaded without transaction management.
The user addressed by means of the ABORT-LOCK-SEQUENCE administration statement must be in a lock sequence. You can use the SHOW-USERS statement (see "SHOW-USERS") to find out whether there is a lock sequence active for a specific user.
On input of the next statement, the addressed user receives a message indicating that the lock sequence has been terminated.
ABORT-LOCK-SEQUENCE |
USER = <user-identification> |
Operands
USER = <user-identification>
Identifies the user whose lock sequence is to be terminated. The identification must be fully qualified (see the section “Syntax for the identification of users”).
Administration command in ISP format and at the CALL DML interface
The LSQ,ABORT administration command corresponds to the ABORT-LOCK-SEQUENCE administration statement here.
LSQ,A[BORT],user-identification
user-identification must be unique. You therefore have to specify all the relevant partial qualifications.