Events Reported to the Event Exit

MVS™ reports the following specific events to the event exit of connected users to a structure. N/A in a column means that the information is not applicable.

For all events, connection information about the connection that is the subject of the event is passed in IXLYEEPL. The connector information includes connect name, connection identifier, and connection disposition.

Table 1. Summary of Events Reported to the Event Exit
Event/Description	Important Information Passed to Event Exit	Connections Notified	Response Required by Notified Connection	Valid IXLYEEPL Return Codes
New Connection EEPLNEWCONNECTION The connection (subject of the event) is new to the structure. Existing connected users might receive notification of a new connection before the IXLCONN request for the new connection completes.		All active connections (except the new connection) to the structure	None.	N/A
Existing Connection (active and failed-persistent) EEPLEXISTINGCONNECTION The connection (subject of the event) is currently defined to the structure. An existing connection can be either active or failed-persistent as indicated by field EEPLSTATEACTIVE in IXLYEEPL. Each existing connection event represents one connected user. New connections might receive notification of existing connections before the IXLCONN request for the new connection completes. The end of the list of existing connections is indicated by a dummy event exit parameter list. Note: The dummy IXLYEEPL is indicated by the EEPLDUMMYLASTEVENT flag. When the flag specifies that this is the last event, the only other information in the EEPL is the identification of the connector whose event exit has been driven and general information about the event.	Active or failed-persistent state of the existing connection, connection disposition, user-specified disconnect data.	A new connection to the structure	If existing connection is active, none. If failed-persistent, user protocol of the new connection determines the response.	rc=X'00', X'01', or X'08'. See Return Specifications.
Disconnected or Failed Connection EEPLDISCFAILCONNECTION One of the following has occurred: The connected user (subject of the event) issued IXLDISC. Disconnection reason specified on IXLDISC can be NORMAL , FAILURE, or DELETESTR . End of task, address space, or system has occurred before the connection (subject of the event) issued IXLDISC. Connection has failed.	Indication of lock resources if held by a lock structure. User-specified disconnect data. Indication of whether, during rebuild, the connection was connected to both the new structure and the old structure.	All active connections to the structure	Required	rc=X'00', X'01', or X'08'. See Return Specifications.
Loss of Connectivity to the structure EEPLLOSSCONN The connection has lost physical connection to the coupling facility.	If rebuild was in progress, indication of whether connectivity was lost to the original structure or to the structure allocated for rebuild. An indication of whether or not to delay action.	All active connections to the structure, including those subject connections that have lost connectivity.	None. Recommended that all connections that have lost connectivity issue IXLDISC with REASON= FAILURE when delaying action is not indicated.	N/A
Structure Failure EEPLSTRFAILURE Either a structure in the coupling facility or the coupling facility itself has failed. New connections are denied access. Note that if the failure is for a single structure rather than the entire coupling facility, XES deallocates the failed structure when either there are no active connections or when the last Rebuild Cleanup event exit has been received as part of the rebuild process.		All active connections to the structure	None. Recommended that all users issue IXLDISC with REASON= FAILURE or rebuild the structure.	N/A
Rebuild Quiesce EEPLREBUILDQUIESCE Rebuild processing has been initiated for the structure. Connections can participate in rebuilding the structure, stop the process, or disconnect.	Reason for the rebuilding or duplexing request. LESSCONN- ACTION and LOCATION attributes for the rebuilding or duplexing request.	All active connections to the structure	If connections decide to rebuild or duplex, connection must Complete outstanding structure requests which, if based on a restart token, should be fully completed before quiescing use of the structure. Stop activity to structure. Prevent new IXLCACHE, IXLLIST, IXLLOCK, or IXLRT requests to the structure. Provide an event exit response. Event response required through IXLEERSP.	rc=X'08'. See Return Specifications.
Rebuild Connect EEPLREBUILDCONNECT All connections have responded to the Rebuild Quiesce event for the structure.		All active connections to the structure	Required. To continue with the user-managed rebuild processing (rebuild or duplexing rebuild), each active connection must issue IXLCONN with the REBUILD option. Once connected to the new structure, connected users can perform coupling facility operations to the structure. To confirm that a connected user has completed its structure reconstruction or data propagation to the new structure, issue IXLREBLD REQUEST=COMPLETE.	N/A
Rebuild Connects Complete EEPLREBUILDCONNECTSCOMPLETE All connections eligible to rebuild-connect to the structure have issued IXLCONN REBUILD. The system indicates the number of successful and unsuccessful connections to the new structure and identifies the connections through the connection ids. Users can determine from their protocol if enough connections are available to continue rebuilding the structure or stop rebuilding.	Indication of the connections that successfully connected to the new structure and the connections that failed Total number of successful connections to the new structure Total number of unsuccessful connections to the new structure	All active connections to the structure. Connectors to a structure in the user-managed duplexing process do not receive this event.	None.	N/A
Rebuild New Connection EEPLREBUILDNEWCONNECTION The connection (subject of the event) to the structure is new. Existing connected users to the new structure might receive notification of a new connection before IXLCONN for the new user completes.	Connect name, connection identifier	Active connections that connected to the new structure (other than the one that is the subject of the event)	None	N/A
Rebuild Existing Connection EEPLREBUILDEXISTINGCONNECTION The connection (subject of the event) is currently connected to the new structure. Each Rebuild Existing Connection event represents one connected user. A new connection might receive notification of existing connections before IXLCONN for the new connection completes. The end of the list of existing connections is indicated by a dummy event exit parameter list. For this event, the system reports only successful connections; failed-persistent connections to the new structure are not reported.		The connection that just connected to the new structure	None	N/A
Rebuild Connect Failure EEPLREBUILDCONNECTFAILURE The IXLCONN REBUILD request fails because the task or address space of the requestor abnormally terminated during IXLCONN REBUILD processing and this task is different from the task which owns the original connection.		All active connections to the structure	Required. Connections must cleanup any control information about a successful rebuild connect request that is reported by either a Rebuild New Connection or Rebuild Existing Connection event.	rc=X'00'or X'08'. See Return Specifications.
Structure Duplexing Established EEPLREBUILDDUPLEXESTABLISHED Connectors to the duplexed structures can begin duplexed structure operations.		All active connections to the structure.	None Connectors to the duplexed structures should begin duplexed structure operations.	N/A
Stop Duplexing Rebuild to Switch EEPLREBUILDSWITCH Duplexing rebuild stop processing has been initiated for the structure. Connectors should prepare to switch to the new structure.		All active connectors to the structure.	Required. Connections must quiesce their use of the old and new structures and perform the necessary cleanup. A confirmation is required with IXLREBLD REQUEST= DUPLEXCOMPLETE.	N/A
Rebuild Cleanup EEPLREBUILDCLEANUP Connections to the structure being rebuilt have issued IXLREBLD with REQUEST=COMPLETE to indicate that the rebuild process is complete. Connections to the structure being duplexed have issued IXLREBLD with REQUEST=DUPLEXCOMPLETE to indicate that the duplexing process is complete.		All active connections to the structure	Event response required through IXLEERSP.	rc=X'08'. See Return Specifications.
Rebuild Complete EEPLREBUILDPROCESSCOMPLETE The structure has been successfully rebuilt.		All active connections to the structure	Connectors should resume normal structure operations.	N/A
Rebuild Stop EEPLREBUILDSTOP Rebuild stop processing has been initiated for the structure. For duplexing, the rebuild stop event implies KEEP=OLD.	Reason for stopping the rebuilding process	All active connections to the structure	Connections must Complete outstanding structure requests to both original and new structure which, if based on a restart token, should be fully completed before quiescing use of each structure. Stop activity to structure Prevent new IXLCACHE, IXLLIST, IXLLOCK, or IXLRT requests to the structure. Provide an event exit response. Event response required through IXLEERSP.	rc=X'08'. See Return Specifications.
Rebuild Stop Complete EEPLREBUILDSTOPPROCESS- COMPLETE Stop-rebuilding for the structure is complete.		All active connections to the structure	Connectors should resume normal structure operations.	N/A
User Synchronization Point EEPLUSERSYNCPOINT A connection has defined a new user synchronization point, or all confirmations have been received for a user synchronization point. Connections can use the IXLUSYNC macro to define synchronization points for different processing stages. For example, see Using IXLUSYNC to Coordinate Processing of Events.	Confirmation that the processing for the event is complete. Event associated with the synchronization point. Definition of next synchronization point if specified. Highest user-defined completion code value (or, for connections that disconnect or fail while owing a sync point confirmation, X'0000FFFF', implicitly set by XES).	All active connections to the structure	Required when the event indicates a new synchronization point:. Confirmation using IXLUSYNC REQUEST=CONFIRM or REQUEST= CONFIRMSET. Not required when the event indicates all confirmations have been received.	N/A
Coupling Facility Structure Volatility State Change EEPLVOLATILITYSTATECHANGE The current volatility state of a coupling facility structure has changed.	The current volatility state	All active connections to the structure	None Connection may want to initiate a rebuild of the structure.	N/A
XES Recommend Action EEPLXESRECOMMENDACTION MVS did not initiate rebuild based on the comparison of the rebuild percent specified for the structure and the value calculated by MVS when a loss of connectivity occurs. MVS uses system weights in the active SFM policy to either start rebuild for the loss or advise the connections to disconnect.	The percentage loss of connectivity, based on SFM policy weights.	Active connections that lost connectivity to the coupling facility containing the structure.	Disconnect from the structure.	N/A
Structure Alter Begin EEPLALTERBEGIN A request to alter the structure has been initiated.	The requested target values, the composite for the minimum available entries/elements and EMCs, and ratio change indication specified by the connections. If user-managed duplexing is in effect, status of the old and new structures.	All active connections to the structure.	None. If the requested change is to contract the structure size, cast out or otherwise free up in-use structure resources to facilitate the structure alter processing.	N/A
Structure Alter End EEPLALTEREND The altering of the structure has ended.	The status of the structure as the result of the structure alter processing. If user-managed duplexing is in effect, status of the old and new structures.	All active connections to the structure.	None. Adjust any limits set for your use of the structure based on the changes made to the size and/or apportionment of the altered structure.	N/A
Loss of Connectivity Percentage EEPLLOSSCONNPCTNOTIFY	The percentage loss of connectivity, based on SFM policy weights. If there is no active SFM policy in the sysplex, the percentage loss of connectivity reported is either 100% or 0. There is no guarantee that all connectors will receive the same value.	Active connections that lost connectivity to a coupling facility containing the structure in a user-managed duplexing rebuild.	None	N/A
Structure Temporarily Unavailable EEPLSTRTEMPUNAVAILABLE The structure is temporarily unavailable for processing coupling facility requests because a system-managed process such as rebuild has begun.	The type of system- managed process that is precluding use of the structure. The event sequence number (required for response).	All active connections to the structure.	Required, either through IXLEERSP or by setting return code in IXLYEEPL. IBM® recommends that connections prevent new coupling facility requests (IXLCACHE, IXLLIST, IXLLOCK, IXLRT, or IXLSYNCH) to the structure before responding to this event.	rc=X'00', X'08'. See Return Specifications.
Structure State Change EEPLSTRSTATECHANGE The characteristics of the structure may have changed as the result of a system-managed process such as rebuild.	The type of process that caused the structure state change. Current® structure characteristics, including: CFLEVEL CFNAME Volatility state Physical structure version numbers Failure isolation state	All active connections to the structure	None. The connector may inspect the new characteristics of the structure and take appropriate action.	N/A
Structure Available EEPLSTRAVAILABLE A structure that had been temporarily unavailable for processing coupling facility requests because a system-managed process such as rebuild had begun is once again available for processing. Connections may receive notification of structure availability without ever having received a Structure Temporarily Unavailable event. The system presents the Structure Available event upon completion of a system-managed process to inform the connector that activity against the indicated structure may be resumed.	The type of system-managed process that had been precluding use of the structure.	All active connections to the structure.	None. On receipt of this event, connections that had quiesced their activity against the structure in response to the Structure Temporarily Unavailable event may resume submitting requests to the structure.	N/A