Design overview
CICS® support of persistent sessions includes the support of all LU-LU sessions, except LU0 pipeline and LU6.1 sessions. With multinode persistent sessions support, if z/OS® Communications Server fails, LU62 synclevel 1 sessions are restored, but LU62 synclevel 2 sessions are not restored.
- SNPS, single-node persistent sessions
- Persistent sessions support is available, so that Communications Server sessions can be recovered after a CICS failure and restart. This setting is the default.
- MNPS, multinode persistent sessions
- In addition to the SNPS support, Communications Server sessions can also be recovered after a Communications Server or z/OS failure in a sysplex.
- NOPS, no persistent sessions
- Persistent sessions support is not required for the CICS region. For example, a CICS region that is used only for development or testing might not require persistent sessions.
The time specified by the PSDINT system initialization parameter for the region determines how long the sessions are retained. If CICS, z/OS Communications Server, or z/OS fails, if a connection to z/OS Communications Server is reestablished within this time, CICS can use the retained sessions immediately; there is no need for network flows to rebind them.
If CICS fails or undergoes immediate shutdown (by means of a PERFORM SHUTDOWN IMMEDIATE command), z/OS Communications Server holds the CICS LU-LU sessions in recovery pending state, and they can be recovered during startup by a newly starting CICS region. With multinode persistent sessions support, sessions can also be recovered if z/OS Communications Server or z/OS fails in a sysplex.
During an emergency restart of CICS, CICS restores those sessions pending recovery from the CICS global catalog and the CICS system log to an in-session state. This process of persistent sessions recovery takes place when CICS opens its VTAM ACB. With multinode persistent sessions support, if the Communications Server or z/OS fails, sessions are restored when CICS reopens its VTAM ACB, either automatically by the COVR transaction, or by a CEMT or EXEC CICS SET VTAM OPEN command. Although sessions are recovered, any transactions inflight at the time of the failure are abended and not recovered.
Subsequent processing depends on the LU. Clean up and recovery for non-LU6 persistent sessions is similar to that for non-LU6 backup sessions under XRF. Clean up and recovery for LU6.2 persistent sessions maintains the bound session when possible, but in some cases it might be necessary to unbind and rebind the sessions, for example, where CICS fails during a session resynchronization.
When a terminal user enters data during persistent sessions recovery, CICS appears to hang. The screen that was displayed at the time of the failure remains on display until persistent sessions recovery is complete. You can use options on the TYPETERM and SESSIONS resource definitions for the CICS region to customize CICS so that either a successful recovery can be transparent to terminal users, or terminal users can be notified of the recovery, allowing them to take the appropriate actions.
If APPC sessions are active at the time of the CICS, Communications Server or z/OS failure, persistent sessions recovery appears to APPC partners as CICS hanging. The Communications Server saves requests issued by the APPC partner, and passes them to CICS when recovery is complete. When CICS reestablishes a connection with the Communications Server, recovery of terminal sessions is determined by the settings for the PSRECOVERY option of the CONNECTION resource definition and the RECOVOPTION option of the SESSIONS resource definition. You must set the PSRECOVERY option of the CONNECTION resource definition to the default value SYSDEFAULT for sessions to be recovered. The alternative, NONE, means that no sessions are recovered. If you have selected the appropriate recovery options and the APPC sessions are in the correct state, CICS performs an ISSUE ABEND to inform the partner that the current conversation has been abnormally ended.