Restarting a Request that Ends Prematurely

Some IXLCACHE requests can complete prematurely (that is, without fully completing the requested service) if the request exceeds the time-out criteria for the coupling facility or the user's buffer is filled before all data is returned. (Time-out criteria for a coupling facility is model-dependent.) The following IXLCACHE requests can complete prematurely if they exceed time-out criteria:

IXLCACHE REQUEST=DELETE_NAME
IXLCACHE REQUEST=DELETE_NAMELIST
IXLCACHE REQUEST=CROSS_INVAL
REQUEST=CROSS_INVALLIST
IXLCACHE REQUEST=RESET_REFBIT
IXLCACHE REQUEST=READ_DIRINFO
IXLCACHE REQUEST=READ_COCLASS
IXLCACHE REQUEST=READ_COSTATS
IXLCACHE REQUEST=UNLOCK_CASTOUT
IXLCACHE REQUEST=REG_NAMELIST
IXLCACHE REQUEST=CASTOUT_DATALIST
IXLCACHE REQUEST=WRITE_DATALIST

There are two methods by which the system enables restart of a prematurely completed request. One method uses a restart token, and the other uses an index value. Both methods require that you provide an answer area, mapped by the IXLYCAA macro.