PSTYPE

The default setting, SNPS (single-node persistent sessions), means that persistent sessions support is available, so that z/OS Communications Server sessions can be recovered after a CICS failure and restart. MNPS (multinode persistent sessions) means that, in addition to the SNPS support, z/OS Communications Server sessions can also be recovered after a z/OS Communications Server or z/OS® failure in a sysplex (across LPARs).

For single-node persistent sessions support, you require z/OS Communications Server V3.4.1 or later, which supports persistent LU-LU sessions. CICS Transaction Server for z/OS, Version 5 Release 2 functions with releases of z/OS Communications Server earlier than V3.4.1, but in the earlier releases sessions are not retained in a bound state if CICS fails. For multinode persistent sessions support, you require z/OS Communications Server V4.R4 or later, and z/OS Communications Server must be in a Parallel Sysplex® with a coupling facility.

If you specify SNPS or MNPS, set a nonzero value for the PSDINT system initialization parameter, which specifies the retention time for session information. The default is zero, which means that sessions are not retained.

If you do not require persistent sessions support, specify NOPS. A CICS region that is used only for development or testing might not require this support. Removing persistent sessions support where it is not required reduces resource consumption, and can enable you to increase the number of CICS regions in an LPAR. If you specify NOPS, a zero value is required for the PSDINT system initialization parameter.