For information pertaining to how an application identifies and restores sessions pending recovery, see Restoring sessions pending recovery. For multinode persistent sessions, any sessions that involve partners on the same VTAM® that recovers a persistence-enabled application are not maintained. Also note that the CID of a session recovered after a node failure is not the same as the CID of the session before the failure.

If the application is going to just clear, (for example, reset by way of SESSIONC CONTROL=CLEAR and SESSIONC CONTROL=SDT), the session after doing a OPNDST RESTORE, rather than resuming the session traffic transparently, then consider setting NIBTRNCK when establishing the session with the OPNDST (ACQUIRE or ACCEPT) or OPNSEC. This will reduce the overhead required to write the session state date to the coupling facility during session traffic.