Effect of z/OS Communications Server persistent sessions support for DTP conversations on APPC sessions
If you enable z/OS® Communications Server persistent sessions support in the local CICS®, after a CICS failure APPC sessions are held in recovery pending state until CICS restarts, or until the timeout value set on the PSDINT system initialization parameter expires. DTP applications that use APPC sessions defined as persistent are affected by persistent sessions recovery.
Remote partner programs can cause excessive queuing delays in the partner system if they continue to issue commands on persistent APPC sessions after this CICS has failed. There is no way for the partner to know that persistent sessions recovery is in progress. However, there are various actions you can take to reduce the risk of new work building up for a connection to a persisting CICS system.
- In DTP applications, requests for sessions are instigated by EXEC CICS ALLOCATE commands. Control
the overall number of queued session requests by using:
- The QUEUELIMIT and MAXQTIME options on the CONNECTION definition
- An XZIQUE global user exit program.
These methods are described in Managing allocate queues.
- Control individual session requests by coding the NOQUEUE|NOSUSPEND option on EXEC CICS ALLOCATE commands.
- Force mapped APPC RECEIVE or CONVERSE commands to time out if there is any delay in receiving expected data, by coding the RTIMOUT option on PROFILE definitions.
- Code a PSDINT value that takes into account the number of your APPC sessions to partner systems.
After a restart, LU6.2 session names, in the range -AAA to -999, are allocated on a "first free" basis (rather than on a "next in the sequence" followed by "last free" basis). This may affect applications that use LU6.2 CONVIDs as external qualifiers.
For further information about z/OS Communications Server persistent sessions support, see Recovery with z/OS Communications Server persistent sessions.