Completing Outstanding Structure Requests

Before responding to the Rebuild Quiesce event, users should complete any request that needs to be restarted because it either exceeded the time-out criteria for the coupling facility or requires more buffer space to return all requested information. In these situations, the system returns either a restart token (from certain IXLCACHE, IXLLIST, and IXLRT invocations) or an entry identifier (from certain IXLLIST and IXLRT invocations).

It is important to remember that after a structure is rebuilt, the new structure may not be an identical copy of the old structure. Specifically,

Information in the restart token used to access the old structure will not be valid for continued operations on the new structure.
Entry ID values will differ between the old structure and the new structure.
Depending on the exploiter's protocol, not all entries or data present in the old structure will necessarily be present in the new structure.
Depending on the exploiter's protocol, the order of lists that have been rebuilt in the new structure (for example, lists of record data within a lock structure) may differ between the old structure and the new structure.

For these reasons, users should not have any outstanding restart tokens (RESTOKENs or EXTRESTOKENs) or entry identifiers (ENTRYIDs) that are to be used to redrive processes after replying to the Rebuild Quiesce event. Users should always fully complete these types of requests before replying to the Rebuild Quiesce event.

Once a user has responded to the Rebuild Quiesce event, the user's connect token is temporarily invalidated to prevent any new accesses to the structure. Therefore, it might be necessary to purge outstanding requests before responding to the Rebuild Quiesce event.

List, Serialized List, and Cache Structures
Use IXLPURGE to purge outstanding IXLLIST or IXLCACHE operations on these structures. Do not respond to the Rebuild Quiesce event until receipt of a confirmation of the completion of each of these outstanding IXLLIST and IXLCACHE events.
Lock Structures
IXLPURGE cannot be used to purge outstanding IXLLOCK requests. Use IXLUSYNC to ensure that all users have recognized the Rebuild Quiesce event and that no connector has issued IXLREBLD REQUEST=STOP. Use IXLPURGE to purge outstanding IXLRT operations. Do not respond to the Rebuild Quiesce event until all outstanding IXLRT operations are complete.

After the Rebuild Quiesce event has been provided, the system handles exit routines as follows:

The system does not prevent the contention, complete, and notify exits from being driven for events related to the original structure. However, the connector can optionally defer the contention exit during the rebuild processing. See Contention Exit Processing for a description of how the contention exit can be deferred.
The system disables the list transition exit for a structure that is being rebuilt when the connected user responds to the Rebuild Quiesce event. The list transition exit remains disabled until either a Rebuild Complete or Rebuild Stop Process Complete event is presented to the user's event exit.

Note that the invalidation of the connect token after the Rebuild Quiesce event is temporary. XES revalidates the original CONTOKEN later in the process when either the structure rebuild is complete or the rebuild is stopped (and all events have been acknowledged). Users will use the original CONTOKEN to access the new structure when it is rebuilt. The user is unable to access the original structure.