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


Restarting a REG_NAMELIST Request that Ends Prematurely

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

The IXLCACHE REQUEST=REG_NAMELIST request can complete prematurely. When a request completes prematurely, the system will not have processed all the registration blocks identifying the data items. To continue processing the registration blocks, you must restart the request.

Be sure to process the information returned from this request before reissuing the request. The data returned from this request will be overwritten if you specify the same buffer address. Continue to reissue the request until the return code indicates that all processing has completed.

When a request completes prematurely, the system returns an index value into the list of registration block entries. This value is returned in the CAARNLINDEX field of the answer area. Use this index value to restart the request.

Reasons for which a REG_NAMELIST can complete prematurely are:
  • The request has exceeded the model-dependent time-out criteria. The index of the next registration block to be processed is returned in the answer area (ANSAREA). All registration blocks preceding this one are processed.
  • The user has specified an incorrect storage class or the target storage class is full. The index of the failing registration block is returned in the answer area. All registration blocks preceding the failing registration block are processed.
  • The user has specified an incorrect local cache vector index. The index of the failing registration block is returned in the answer area. None of the registration blocks are processed.
The information in the NSBAREA for the registration blocks processed before the premature completion of the REG_NAMELIST request might or might not contain meaningful information. The following return and reason codes from the REG_NAMELIST request indicate which registration blocks were processed prior to the request's premature completion.
IXLRETCODEOK
All NSB array and NSBINVLCVINUM array entries that have an index value greater than or equal to STARTINDEX and less than or equal to ENDINDEX contain meaningful information.
IXLRSNCODETIMEOUT
All NSB array and NSBINVLCVINUM array entries that have an index value greater than or equal to STARTINDEX and less than CAARNLINDEX contain meaningful information. To process the remaining registration blocks, update STARTINDEX with the value in CAARNLINDEX and reissue the REG_NAMELIST request.
IXLRSNCODESTRFULL IXLRSNCODEBADSTGCLASS
All NSB array and NSBINVLCVINUM array entries that have an index value greater than or equal to STARTINDEX and less than CAARNLINDEX contain meaningful information. The registration block indexed by CAARNLINDEX was not processed either because the target storage class was full or because an incorrect storage class was specified. If possible, correct the error in the registration block. To process the remaining registration blocks (including the corrected registration block), update STARTINDEX with the value in CAARNLINDEX and reissue the REG_NAMELIST request. If it is not possible to correct the error in the registration block, update STARTINDEX with the value in CAARNLINDEX plus one and reissue the REG_NAMELIST request.
IXLRSNCODEBADVECTOROP
No NSB array or NSBINVLCVINUM array entries contain meaningful information. The registration block indexed by CAARNLINDEX contains the invalid vector index. Correct that vector index value and reissue the REG_NAMELIST request with the same STARTINDEX and ENDINDEX values.

A restarted request can also complete prematurely due to either a timeout or a failure on a later registration block in the list. Restart the request using the procedure described.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014