User-Managed Rebuild Events and the Event Exit

All active connectors to a structure are required to participate in the user-managed rebuild process for that structure. During the course of the rebuild, events are presented to the event exits of all connectors to the structure. The events notify the connected users of the start or completion of specific phases of the rebuild process. The connected user must respond to some, but not all, of these events.

The following list summarizes the events that the system reports about the rebuild process to the event exit and the responses expected by the event exits:

Rebuild Quiesce: Request to start structure rebuild processing. The IXLYEEPL will indicate the type of rebuild (rebuild or duplexing rebuild). (Response is required via IXLEERSP.)
Rebuild Connect: Request to issue IXLCONN REBUILD for the structure after all connectors have quiesced the use of the structure. When the connector has propagated all required data to the new structure, it must confirm that this processing is complete with IXLREBLD REQUEST=COMPLETE. (Response is required, first with IXLCONN REBUILD, and then via IXLREBLD REQUEST=COMPLETE.)
Rebuild Connects Complete: Confirmation that all connected users have issued IXLCONN REBUILD for the structure. This event is not presented to connectors during the duplexing rebuild process.
Rebuild New Connection: New connection to the new structure.
Rebuild Existing Connection: Existing connection to the new structure.
Rebuild Connect Failure: IXLCONN REBUILD failure for a connector because of abnormal task or address space termination. (Response is required via IXLEERSP or in IXLYEEPL).
Rebuild Duplex Established: Duplexing has been established by each connector. Connectors can begin duplexed structure operations. This event pertains only to duplexing rebuild.
Rebuild Switch: Request to switch to using only the new instance of a duplexed structure. Request to issue REQUEST=DUPLEXCOMPLETE after quiescing use of both instances of the structure. This event pertains only to duplexing rebuild. (Response is required via IXLREBLD.)
Rebuild Cleanup: Confirmation that all connected users have completed structure processing and should clean up information related to the old structure which will be deallocated. (Response is required via IXLEERSP.)
Rebuild Process Complete: Confirmation that the structure has been rebuilt.
Rebuild Stop: Request to stop a structure rebuild process. If this is a duplexing rebuild, the request is to stop the duplexing and use the old structure. Connected users must clean up information about the new structure, which will be deallocated. (Response is required via IXLEERSP.)
Rebuild Stop Process Complete: Confirmation that the rebuilding process has been stopped.

Note that user-defined synchronization points can also be used if additional coordination is required for rebuilding a structure. See Using IXLUSYNC to Coordinate Processing of Events.

Some rebuild events require a response from all connected users that are participating in the process. You can confirm the following rebuilding events through the IXLEERSP macro:

Rebuild Quiesce. You must respond to a request for rebuilding the structure after you have quiesced your use of the existing structure. To continue the rebuilding process, issue IXLEERSP with EVENT=REBLDQUIESCE.
Rebuild Cleanup. You must ensure that resources associated with the original structure have been released. To confirm the event, issue IXLEERSP with EVENT=REBLDCLEANUP.
Rebuild Connect Failure. You must respond to the rebuild connect failure after cleaning up any control information. To confirm the event, issue IXLEERSP with EVENT=REBLDCONNFAIL or respond with IXLYEEPL.
Rebuild Stop. You must respond to the stop rebuild request. To confirm the event, issue IXLEERSP with EVENT=REBLDSTOP.

Some rebuilding events can be superseded by a Rebuild Stop event. In these cases, the connector must respond to the Rebuild Stop event rather than to the event that was previously expected. The timing of an event being superseded by a Rebuild Stop event might result in some connectors seeing the superseded event and other connectors not seeing it. Therefore, some connectors might see the prior event and then the Rebuild Stop event; other connectors might never see the prior event and only see the Rebuild Stop event. Note that if a connector responds to an event that has been superseded, the system returns a failing return code to the connector.

The following rebuilding events can be superseded by a Rebuild Stop event:

Rebuild Quiesce
Rebuild Connect
Rebuild Connects Complete
Rebuild Duplex Established

See Delivery of Rebuild Stop Event.