Responding to the Rebuild Cleanup Event

Before providing a response to the Rebuild Cleanup event, all connectors should clean up information related to the structure that will be deallocated. Connectors discard the temporary connect token and the old vector token (if applicable). Note that the vector token returned on the IXLCONN REBUILD is not a temporary token like the connect token. The vector token returned must be used to access the structure after the rebuild has completed. (Users do not have the option to stop the rebuild process at this point. See Stopping a User-Managed Rebuild Process.)

In certain instances, XES must quiesce the activity of user exits in order to perform cleanup processing. For example, when a connector provides an event exit response for the Rebuild Cleanup event, XES will force to completion any user exits that are executing on behalf of that user's connection to BOTH the original and the new structures issuing a PURGEDQ against the appropriate units of work. No new events will be presented to the user exits on behalf of the original structure (as it is being discarded). Normal user exit processing will resume for the rebuilt structure upon completion of the rebuild process.

A user exit must be sensitive to conditions that can occur as a result of actions taken by XES and must be able to handle these as appropriate. For example, if a user exit has suspended itself, when the PURGEDQ is issued the system abends the user exit's unit of work with a retryable X'47B' abend and gives control to the user exit's recovery routine. (Note that although the recovery routine can retry, the user exit can not re-suspend itself because the system will fail any request to suspend a unit of work that has been the target of a PURGEDQ.) If the recovery routine percolates back to the system, its associated connection is terminated.

The rebuild process is actually complete when the Rebuild Process Complete event has been presented to the event exit. From the time that all connectors have issued the IXLREBLD REQUEST=COMPLETE or REQUEST=DUPLEXCOMPLETE and XES begins notifying each connector of the Rebuild Cleanup event until the Rebuild Process Complete event is presented, the rebuild process cannot be stopped and a new rebuild request for the structure cannot be started.

If a REBUILD REQUEST=STOP request is initiated, the request is rejected with reason code IXLRSNCODEINCLEANUP indicating that the rebuild process cannot be stopped during the cleanup phase.
If a REBUILD REQUEST=START request is initiated, the request is rejected with reason code IXLRSNCODEALREADYREBUILDING indicating that a rebuild request already is in progress.

XES notifies connectors of structure failure and/or loss of connectivity to the new structure that occur during the time between when the IXLREBLD REQUEST=COMPLETE is issued and the Rebuild Process Complete event is issued after the event is presented.