PSDINT

The PSDINT system initialization parameter specifies the persistent session delay interval, which states if, and for how long, z/OS® Communications Server holds sessions in a recovery-pending state.

PSDINT={0|hhmmss}
0
If a failure occurs, z/OS Communications Server sessions are terminated. Zero is the default, and means that persistent sessions support is not exploited.
hhmmss
The time for which z/OS Communications Server retains sessions if a failure occurs, from 1 second up to the maximum of 23 hours 59 minutes and 59 seconds. Specify a 1 to 6-digit time in hours, minutes, and seconds. If you specify fewer than six digits, CICS® pads the value with leading zeros. Thus, a value of 500 is taken as 5 minutes exactly.
You can override this value while CICS is running. Overriding the value changes the action taken by z/OS Communications Server if a failure occurs. The changed interval is not stored in the CICS global catalog, and therefore is not restored in an emergency restart.

z/OS Communications Server holds all sessions in a recovery-pending state for up to the interval specified, unless they are unbound through path failure or z/OS Communications Server operator action, or other-system action in the case of intelligent LUs. 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.

  • If you specify SNPS (the default) or MNPS for the PSTYPE system initialization parameter for the CICS region, set a nonzero value for the persistent session delay interval, so that sessions are retained.
  • If you specify NOPS (no persistent sessions support) for the PSTYPE system initialization parameter, a zero value is required for the persistent session delay interval.
When choosing your PSDINT value, take account of the types and numbers of sessions involved. You must exercise care when specifying large PSDINT values because of the problems such a value might give in some environments, in particular:
  • Dial up sessions, for which real costs might be incurred.
  • LU6.2 sessions to other host systems. If these sessions are retained in recovery pending state, the other host systems might experience excessive queuing delays. This point applies to LU6.1 sessions that are retained until restart, when they are unbound.