Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Cleanup session z/OS Communications Server: SNA Programming SC27-3674-00 |
|||||||||||||
For certain types of session outages, see Session outage notification (SON) codes on UNBIND. VTAM® sends the application program a CLEANUP request unit. Arrival of the CLEANUP request unit at an application program causes the program's NSEXIT exit routine to be scheduled (if one exists). Because VTAM has completely terminated the session, the exit routine does not take any action to end the session (that is, it does not issue a CLSDST or TERMSESS macroinstruction). The exit routine can clean up application program control blocks for the session. The exit routine can also attempt to reestablish the session, and the attempt can be successful if the cause of the session outage has been repaired or bypassed, and the desired LU is available. The format of the CLEANUP request unit is shown in Figure 1. Figure 1. Format of a Cleanup Session request
unit
If a PLU application program does not have an SCIP exit routine or has SONSCIP=NO coded on its APPL definition statement, any UNBIND it receives is converted to a CLEANUP for processing by the NSEXIT exit routine. When the application program involved in a disrupted session is acting as the PLU and does not have an NSEXIT exit routine, that program's LOSTERM exit routine (if one exists) can be scheduled to report loss of the session. See Session outage notification. An application program acting as an SLU must have an NSEXIT exit routine or else it receives no notification of sessions being cleaned up. Even if no other action is taken, the NSEXIT exit routine should set registers 0 and 15 to 0 before returning to VTAM.
|
Copyright IBM Corporation 1990, 2014
|