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


Processing an UNLOCK_CASTOUT Request that Ends Prematurely

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

The completion of IXLCACHE REQUEST=UNLOCK_CASTOUT request can be affected for the following reasons:
  • The request exceeds the time-out criteria for the coupling facility. (Time-out criteria is model-dependent.)
  • A name element specified a data item that is not defined to the cache structure.
  • The connection specified on the CONTOKEN keyword, or the process or task specified on the PROCESSID keyword, does not hold the cast-out lock for one of the data items specified by the name element.
  • A name element specified a data item with parity bits that are not valid.
  • A name element specified a data item that holds a cast-out lock in a write-with-cast-out state. The write-with-cast-out lock state is not compatible with the change indicator for the data item.
Each time a request completes prematurely, the system returns an index value into the list of name elements in the CAAULINDEX field of the answer area. Use this index value in CAAULINDEX to:
  • Locate the name element that specified the undefined data item, the data item with a connector, task, or process that does not hold the cast-out lock, the data item that specified parity bits that are not valid, or the data item that requested an incompatible update for the change indicator.
  • For time-out problems, restart the request so it can process the remaining elements in the list of name elements.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014