Identify that a holder has released resource (ENQRLSE)

Use the ENQRLSE SYSEVENT to notify SRM that the holder of a resource causing contention has released the resource. The inputs must be the same as those for the ENQHOLD SYSEVENT previously issued for the holder including the specification of parameter TYPE=3. See the description of ENQHOLD for considerations related to using enclaves for tasks that serialize resources. Do not issue SYSEVENT ENQRLSE if you have selected the short time/high frequency enqueue promotion.

Input register information

If this SYSEVENT is invoked with the TYPE=3 keyword, then register 1 must point to a parameter list. The parameter list must be non-pageable and addressable via the caller's primary address space. To map the parameter list, use the IRAEVPL mapping macro described in z/OS MVS Data Areas in z/OS Internet Library at http://www.ibm.com/systems/z/os/zos/bkserv/.

Return and reason codes

When processing is complete for the ENQRLSE SYSEVENT, the last byte of register 15 contains one of the following hexadecimal return codes:

Table 1. Return Codes for ENQRLSE
Return Code	Meaning
00	Successful completion.
08	Enclave token is invalid.
10	The ASID specified did not map to a valid, active address space. This may occur because the address space it represents is no longer active or was never active. Note: Only valid if parameter IraEnqHR_FLAGS_RhTerm=1 was specified in the parameter list.
12	The STOKEN specified did not map to a valid, active address space. This may occur because the address space it represents is no longer active or was never active. Note: Only valid if parameter IraEnqHR_FLAGS_RhTerm=1 was specified in the parameter list.
16	Invalid combination of ASID, STOKEN, or enclave token was specified in the parameter list. Specify either ASID, or STOKEN, or enclave token.