Situations in which sessions are not reestablished
When z/OS® Communications Server persistent sessions support is in use for a CICS® region, CICS does not always reestablish sessions that are being held by the Communications Server in a recovery pending state. In the situations listed here, CICS or the Communications Server unbinds and does not rebind recovery pending sessions.
- If CICS does not restart within the persistent sessions delay interval, as specified by the PSDINT system initialization parameter.
- If you perform a COLD start after a CICS failure.
- If CICS cannot find a terminal control table terminal entry (TCTTE) for a session; for example, because the terminal was autoinstalled with AIRDELAY=0 specified.
- If a terminal or session is defined with the recovery option (RECOVOPTION) of the TYPETERM or SESSIONS resource definition set to RELEASESESS, UNCONDREL or NONE.
- If a connection is defined with the persistent sessions recovery option (PSRECOVERY) of the CONNECTION resource definition set to NONE.
- If CICS determines that it cannot recover the session without unbinding and rebinding it.
The result in each case is as if CICS has restarted following a failure without Communications Server persistent sessions support.
In some other situations APPC sessions are unbound. For example, if a bind was in progress at the time of the failure, sessions are unbound.
With multinode persistent sessions support, if a Communications Server or z/OS failure occurs and the TPEND failure exit is driven, the autoinstalled terminals that are normally deleted at this point are retained by CICS. If the session is not reestablished and the terminal is not reused within the AIRDELAY interval, CICS deletes the TCTTE when the AIRDELAY interval expires after the ACB is reopened successfully.