Releasing Ownership of a Resource (REQUEST=RELEASE)

Use the RELEASE request to relinquish ownership of a resource or to replace a request to OBTAIN or ALTER the resource that is pending on the contention exit resource request queue with a more current request to release it (in effect, cancelling the pending request).

You can only release a resource of which you are the owner or for which you have a pending request. Otherwise, the system rejects the RELEASE request with return and reason codes.

On an IXLLOCK RELEASE request you can modify the user data and the record data and also specify the disposition of the record data associated with the resource request.

User data
The user data (which may or may not have been modified by the contention exit) is returned in the UDATAVAL area in the IXLLOCK parameter list for requests that complete synchronously and the CMPLUDATA field for asynchronous requests.
Record data
On a RELEASE request you can specify what to do with the record data entry associated with the resource. The RDATA keyword indicates whether to delete, to keep, or to keep and update this record data entry. Note that keeping the record data in the coupling facility lock structure allows ownership information to remain and continue to be available to connected users after the ownership of the resource has been released. However, it is the responsibility of the connected users to either reacquire or free these record data entries.