Use the index value to restart a prematurely completed request. Before restarting a request, you must reinitialize the index value that FIRSTNAME specifies. If the request exceeded a time-out value for the coupling facility, reinitialize the FIRSTNAME index value to the value returned in CAAULINDEX.

If the request specifies a data item that is not in the cache structure, a data item for which the connection, task, or process does not hold the cast-out lock, a data item that specified parity bits that are not valid, or a data item that requested an incompatible update for the change indicator, and the condition is unexpected, check to ensure that all users of the cache structure are following the established protocols. If your protocol expects these conditions to occur and you want to restart the request, increase the value in the CAAULINDEX by 1 (as long as the original value is not the last element in the list), so that it points to the next name element in the list. When you reissue the request, specify the new index value on FIRSTNAME.

In the previous example that described missing data item C indicated by index value 3 in CAAULINDEX, specify 4 in CAAULINDEX. Then for FIRSTNAME, also specify 4 and reissue the request. When you reissue the request, the system can start to release the cast-out lock starting with data item D.

To restart a request, after reinitializing FIRSTNAME, reissue IXLCACHE REQUEST=UNLOCK_CASTOUT. 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 FIRSTNAME) as the request that completed prematurely. For general information about restarting requests, see Restarting a Request that Ends Prematurely.