z/OS MVS Programming: Sysplex Services Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Releasing a Single Cast-Out Lock: Summary

z/OS MVS Programming: Sysplex Services Guide
SA23-1400-00

You use an UNLOCK_CO_NAME request to unlock one lock that your connection, or optionally your process or task, holds.

The request must identify the data item whose cast-out lock is to be unlocked.
  • To identify the data item, build a name element in the area specified by CUNBAREA, mapped by IXLYCUNB. Each name element contains the data item name, user-defined data, parity bits, and a change indicator (change-bit-overindication bit):
  • To mark the data item as changed use the CUNBCHANGEOI field in the IXLYCUNB mapping macro. The data item remains associated with its specified cast-out class, and the resources of the data item are not available for reclaim.
  • If the data item is not changed, allow the system to leave the state of the data item as is, and the data item is disassociated with its cast-out class and its resources available for reclaim.

Optionally, specify the task or process identifier on the PROCESSID keyword to identify the task or process that holds the cast-out lock for the data item.

The request can alter the directory entry for the data item. If, while you hold the cast-out lock, no other user writes changed data to the data item, the system updates the directory entry with the information you supply in the name element. If another user writes changed data to the data item while you hold the cast-out lock, the system unlocks the cast-out lock but ignores your directory update information. Instead, the system updates the directory with information provided by the user who performed the update.

There are other keywords that are required and some that are optional. For a description of keywords that are applicable to all IXLCACHE requests, see:

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014