Handling Connection Failures during Synchronization

Whenever a connection terminates, the system informs all connected users through the Disconnected or Failed Connection event. If the connection terminates while a user event is set, two options are available.

An active connector confirms any outstanding user event confirmations on behalf of the disconnected or failed connection using PROXYRESPONSE=YES before all connectors have responded to the Disconnected or Failed Connection event.
The system confirms all outstanding user event confirmations for the disconnected or failed connection as soon as all connectors have responded to the Disconnected or Failed Connection event.

Before responding to the Disconnected or Failed Connection event, the other connected users have an opportunity to complete the failed user's processing for the user event and respond to the event, if required. An example of when this might be most useful is when the CONFIRMSET option is used. If the failed user was the last connector to issue IXLUSYNC and had specified CONFIRMSET, the next event might not have been set before the user terminated. In such a case, one or more of the peer connectors could issue a SET to define the next event.

To confirm a user event on behalf of a failed user, the active connector must provide the connect token of the failed user. The system makes this token available when reporting the Disconnected or Failed Connection event.

If all connections terminate, the system resets the user event.

Connecting to a Structure when a Synchronization Point Is Set describes XES processing when new connectors connect to a structure while a user synchronization point is set.