Defining z/OS Communications Server persistent sessions support

If you choose to run a CICS® region with z/OS® Communications Server persistent sessions support, terminal users can have their sessions recovered and continue working in the event of a CICS or z/OS Communications Server failure.

About this task

Use the CICS system initialization parameters PSTYPE and PSDINT to set up persistent sessions support for a CICS region, and use options on the CONNECTION, TYPETERM, and SESSIONS resource definitions to customize the user experience for terminal users in the event of a recovery.

The default settings for the PSTYPE and PSDINT system initialization parameters mean that persistent sessions support is available to the CICS region, but that it is not being exploited. Recovery with z/OS Communications Server persistent sessions explains what happens when you exploit persistent sessions support, and why you might want to run a CICS region without persistent sessions support.

The default values for RECOVOPTION and RECOVNOTIFY in TYPETERM definitions are SYSDEFAULT and NONE respectively but when used in this combination with persistent sessions can, in some circumstances, result in a recovered terminal becoming unusable. This condition can continue until a task is automatically initiated at the terminal, for example using EXEC CICS START TRANSID(xxx) TERMID(yyy). While use of RECOVNOTIFY(NONE) may be appropriate for devices such as printers different values should be considered for user terminals.

If you want to change the type of persistent sessions support for an existing CICS region, you need to shut down the region and perform a cold start with the new settings. You cannot change between single-node persistent sessions support, multinode persistent sessions support, and no persistent sessions support while CICS is running. Because the persistence characteristics of a bound session are established when the session is created, you need to force an unbind and to rebind the sessions to acquire the correct persistence characteristics for the new level of persistent sessions support requested by CICS. The most straightforward way to achieve this is to carry out a cold or initial start of the CICS region.

You can change the persistent sessions delay interval while CICS is running, but the changed interval is not stored in the CICS global catalog, and therefore is not restored in an emergency restart.

If you do want to use persistent sessions support for a CICS region, follow these steps:

Procedure

  1. Use the PSTYPE system initialization parameter to specify an appropriate level of persistent sessions support.
    1. If you have z/OS Communications Server V4R4 or later, in a Parallel Sysplex® with a coupling facility, specify MNPS for multinode persistent sessions support. This level of support enables recovery in the event of a z/OS Communications Server, z/OS, or CICS failure.
    2. If you do not have suitable facilities for multinode persistent sessions support, specify SNPS for single-node persistent sessions support. This level of support enables recovery in the event of a CICS failure, but not in the event of a z/OS Communications Server or z/OS failure.
  2. Use the PSDINT system initialization parameter to specify a suitable persistent sessions delay interval. This value determines for how long z/OS Communications Server holds sessions in a recovery-pending state. The interval you specify must be able to cover the time from a CICS failure to the time when the z/OS Communications Server ACB is opened by CICS during a subsequent emergency restart.
  3. Choose and set an appropriate value for the RECOVOPTION option of the SESSIONS and TYPETERM resource definitions used in the CICS region. Typically, this value can be the default SYSDEFAULT, which makes CICS select the optimum procedure for recovering sessions. This setting means that in the event of a recovery, the terminal user can clear the screen and continue to enter CICS transids.
  4. Choose and set an appropriate value for the RECOVNOTIFY option of the TYPETERM resource definitions used in the CICS region.
    1. If you want a successful recovery to be transparent to terminal users, specify NONE.
    2. If you want to display a message on the screen to say that the system has recovered, specify MESSAGE.
    3. If you want to start a transaction at the terminal, such as the good-morning transaction, specify TRANSACTION.
  5. If you are working with an existing CICS region, perform a cold start of the CICS region to implement the changes to persistent sessions support.


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