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
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: