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.

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.



dfht2c0054.html | Timestamp icon Last updated: Sunday, 4 June 2017