Table 67 summarizes the lock manager domain’s specific gate. It shows the level-1 trace point IDs of the modules providing the functions for the gate, the functions provided by the gate, and whether or not the functions are available through the exit programming interface (XPI).
Gate | Trace | Function | XPI |
---|---|---|---|
LMLM |
LM 0003 LM 0004 |
ADD_LOCK DELETE_LOCK LOCK UNLOCK TEST_LOCK_OWNER |
NO NO NO NO NO |
The ADD_LOCK function of the LMLM gate is used to add a named lock to LM’s state.
OK|INVALID|DISASTER|KERNERROR
RESPONSE | Possible REASON values |
---|---|
DISASTER |
INSUFFICIENT_STORAGE ABEND LOOP |
The LOCK function of the LMLM gate is used to request the lock.
EXCLUSIVE|SHARED
CICS|NO
OK|EXCEPTION|PURGED|INVALID|DISASTER|KERNERROR
RESPONSE | Possible REASON values |
---|---|
DISASTER |
INSUFFICIENT_STORAGE ABEND LOOP |
EXCEPTION |
LOCK_TOKEN_NOT_FOUND DUPLICATE_LOCK_OWNER LOCK_BUSY |
Note:
DUPLICATE_LOCK_OWNER is
returned when a resource requests a lock twice without unlocking during the
same task: this is often treated in the same way as OK by the requesting resource. |
The UNLOCK function of the LMLM gate is used to release the lock.
EXCLUSIVE|SHARED
OK|EXCEPTION|INVALID|DISASTER|KERNERROR
RESPONSE | Possible REASON values |
---|---|
DISASTER |
ABEND LOOP |
EXCEPTION |
LOCK_TOKEN_NOT_FOUND SHARED_LOCK_FREE NOT_LOCK_OWNER |
The TEST_LOCK_OWNER function of the LMLM gate is used to test the owner of a lock for self.
OK|EXCEPTION|INVALID|DISASTER|KERNERROR
RESPONSE | Possible REASON values |
---|---|
EXCEPTION |
LOCK_TOKEN_NOT_FOUND NOT_LOCK_OWNER |
DISASTER |
ABEND LOOP |
The DELETE_LOCK function of the LMLM gate is used to delete the named lock from LM’s state.
OK|EXCEPTION|INVALID|DISASTER|KERNERROR
RESPONSE | Possible REASON values |
---|---|
DISASTER |
ABEND LOOP |
EXCEPTION |
LOCK_TOKEN_NOT_FOUND NOT_LOCK_OWNER |