A connection to a coupling facility structure might be in one of
four states, as defined below. You can use the IXCQUERY macro and
the DISPLAY XCF operator command to determine the state of a connection.
- Undefined state — The connection does not exist.
- Active state — The connection is active.
- Failed-persistent state — The connection has abnormally
terminated or disconnected with REASON=FAILURE and all event exit
responses have been received. All event exit responses from peer
connections indicated that the connection should not be released.
- Disconnecting or failing state — The connection has disconnected
with REASON=NORMAL or REASON=DELETESTR (disconnecting
state) or has been abnormally terminated or disconnected with REASON=FAILURE
(failing state). All event exit responses have not yet been received
for the disconnection or failure of the connection.
If a user issues
IXLCONN with the same connection name as the connection in the disconnecting
or failing state, IXLCONN rejects the request with reason code IXLRSNCODERSPNOTREC.
(See the IXLYCON macro for a description of all XES reason codes.)
While
the connection is in the disconnecting or failing state, you cannot
force the connection with the IXLFORCE service or the SETXCF FORCE
command.
When all event exit responses are received, the connection
is placed either in the undefined state (the connection does not exist)
or the failed-persistent state.
Figure 1 shows the events that can cause
a connection to change from one state to another.
Figure 1. Connection State Transitions: Undefined,
Active, Disconnecting, Failing