Enabling of persistence

CICS® requests persistent sessions support when it opens the z/OS® Communications Server ACB.

Summary

  1. z/OS Communications Server ACB opened with PARM=PERSIST=YES
  2. z/OS Communications Server levels checked.
  3. z/OS Communications Server SETLOGON OPTCD=PERSIST or NPERSIST

More detail

Persistence is enabled as follows:
  1. The z/OS Communications Server ACB is opened with PARM=PERSIST=YES, specified in DFHTCTPX.
  2. DFHZSLS calls DFHZGSL to issue SETLOGON OPTCD=PERSIST/NPERSIST. DFHZSLS copies 8 bytes of z/OS Communications Server information into the TCT prefix. These bytes contain details of the z/OS Communications Server level and the functions that it supports. Releases of CICS that did not support persistent sessions copied only 4 bytes of z/OS Communications Server data.
The use of persistent sessions depends on the level of z/OS Communications Server being at least V3R4.1 for single-node persistent sessions support. This level of z/OS Communications Server returns more function bit data to CICS than previous versions and supports the use of persistent sessions. Checks are made by CICS of the current z/OS Communications Server level and the z/OS Communications Server level against which the TCT was generated. If either level is not high enough, parameters relating to the use of persistent sessions are not used when macros are called.


dfhs3c001134.html | Timestamp icon Last updated: Monday, 5 June 2017