Interconnected CICS environment, recovery and restart
CICS® systems can be interconnected using MRO, LU6.1, or LU6.2 connections and sessions. Recovery and restart behavior varies depending on the session type and whether or not z/OS® Communications Server persistent sessions support is used.
MRO sessions
MRO connections cannot persist across CICS failures and subsequent emergency restarts.LU6.1 sessions
If a CICS region fails in a multisystem environment, all the LU6.1 sessions that are connected to it are held in recovery pending state until it is restarted with an emergency restart or until the expiry of the persistent session delay interval. In either case, the LU6.1 sessions are then unbound. They need to be reacquired before they can be used again.Slightly different symptoms of the CICS failure are presented to the systems programmer or operator, depending on whether persistent sessions support is used. In systems without persistent sessions support, all the LU6.1 sessions unbind immediately after the failure.
In a system with persistent session support, the LU6.1 sessions are not unbound until the emergency restart, if this occurs within the persistent session delay interval, or the expiry of the persistent session delay interval. Consequently, these sessions might take a longer time to be unbound.
LU6.2 sessions
LU6.2 sessions that connect different CICS systems are capable of persistence across the failure of one or more of the systems and a subsequent emergency restart within the persistent session delay interval.- Sessions for which no catalog entry is found:
- Autoinstalled LU6.2 parallel sessions.
- Autoinstalled LU6.2 single sessions initiated by BIND requests.
- Autoinstalled LU6.2 single sessions initiated by z/OS Communications Server VTAM® CINIT requests, if the AIRDELAY system
initialization parameter is set to zero. (AIRDELAY specifies
the interval that elapses after an emergency restart before autoinstalled
terminal entries that are not in session are deleted.)
In other words, the only autoinstalled LU6.2 sessions that are not unbound are single sessions initiated by CINIT requests, and then only if AIRDELAY is greater than zero.
- All sessions on an LU6.2 connection to a failing TOR, where, on one or more of the sessions, an AOR has function-shipped an ATI request to the TOR, because the request is associated with a terminal owned by the TOR. ATI-initiated transaction routing is described in Traditional routing of transactions started by ATI.
- All sessions on an LU6.2 connection, where, on one or more of the sessions, transaction routing by means of CRTE is taking place but no conversation is in progress at the point of the failure. Where a conversation is in progress, a DEALLOCATE(ABEND) is sent to the partner of the failing CICS.
After the failure of CICS in an LU6.2 interconnected environment, and a subsequent emergency restart within the persistent session delay interval, transaction CLS1 (CNOS) is not run unless one side of the connection issued a CNOS request to zero or the connection was in the process of CNOS negotiation at the time of the failure.
The failing system runs transaction CLS2 (XLN, exchange log names) as soon as it can after emergency restart within the persistent session delay interval. CLS2 must run before any further synclevel 2 conversations can be processed by either of the connected systems.