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


Restarting a DELETE_NAMELIST Request that Ends Prematurely

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

An IXLCACHE REQUEST=DELETE_NAMELIST request might complete prematurely if the request exceeds the time-out criteria for the coupling facility (time-out criteria is model-dependent) or a halt condition is found as a result of specifying HALTONCHANGED=YES. Each time a request completes prematurely, the system returns an index value into the list of name elements in the CAADNLINDEX field of the answer area. Use this index value in CAADNLINDEX to restart the request so it can process the remaining elements in the list of name elements. Reinitialize the STARTINDEX index value to the value returned in CAADNLINDEX. To restart a request, after reinitializing STARTINDEX, reissue IXLCACHE REQUEST=DELETE_NAMELIST. To ensure that you do not alter the intent of the request that completed prematurely, the restarted request should specify the same keywords and values (with the exception of the index value specified on STARTINDEX) as the request that completed prematurely. For general information about restarting requests, see Restarting a Request that Ends Prematurely.

For DELETETYPE=DIRANDDATA, a check of the changed status of data and cast-out lock state for a structure entry may be requested prior to processing the structure entry by specifying the HALTONCHANGED=YES keyword. If a structure entry is found to either contain changed data or for which the cast-out lock is currently held, processing of the DELETE_NAMELIST request is halted and the system returns the index value (CAADNLINDEX) into the list of name elements of the entry name meeting the halt criteria in the answer area. When the DELETE_NAMELIST request is halted as requested, the application is expected to take some action to change the state of the indicated structure entry data to unchanged (that is, the cast-out lock is not held and the status of the data is unchanged) before resuming the request. One such action could be to read the entry data for castout, write the data to permanent storage, then reset the cast-out lock to the not-held state. After taking such action, the DELETE_NAMELIST request may be started at the element in the list of name elements that originally caused the request to halt by setting input parameter STARTINDEX to CAADNLINDEX.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014