Summary tables of exit routines

The following tables summarize the exit routines that are discussed in the preceding sections.

Table 1. Summary of exit routines involved in session initiation
Action or event causing session-initiation request	Exit routine ¹ for event that occurs…
Action or event causing session-initiation request	…in application program named PLUAPPL	…in application program named SLUAPPL
LU sends Initiate request or character-coded logon requesting session with PLUAPPL.	LOGON exit routine is scheduled with CINIT.	(Not applicable)
SLUAPPL issues REQSESS requesting session with PLUAPPL.	LOGON exit routine is scheduled with CINIT.	If PLUAPPL accepts CINIT by issuing OPNDST OPTCD=ACCEPT, BIND is received in SCIP exit routine. If, after SSCP responds positively to Initiate resulting from REQSESS, the session cannot be established (for example, PLUAPPL rejects the CINIT), NSEXIT exit routine is scheduled with NSPE or Notify RU.
PLUAPPL issues OPNDST OPTCD=ACCEPT for session with SLUAPPL.	(Not applicable)	BIND received in SCIP exit routine.
PLUAPPL issues OPNDST OPTCD=ACQUIRE for session with SLUAPPL.	(Not applicable)	BIND received in SCIP exit routine.
PLUAPPL issues SIMLOGON for session with SLUAPPL.	LOGON exit routine is scheduled with CINIT. If, after the SSCP responds positively to Initiate resulting from SIMLOGON, the session cannot be established, NSEXIT exit routine is scheduled with NSPE or Notify RU.	If PLUAPPL accepts CINIT by issuing OPNDST OPTCD=ACCEPT, BIND is received in SCIP exit routine.
PLUAPPL is the controlling application program for a device-type LU (LOGAPPL=PLUAPPL in the LU's definition statement), and another PLU releases the LU for which there are dependent queued sessions.	LOGON exit routine is scheduled with CINIT.	(Not applicable)
VTAM® operator issues VARY LOGON command to make PLUAPPL the controlling application program for a dependent LU and the LU is now available.	LOGON exit routine is scheduled with CINIT.	(Not applicable)
Application program named PASSER issues CLSDST OPTCD=PASS to pass SLUAPPL to PLUAPPL.	LOGON exit routine is scheduled with CINIT. (If the requested session cannot be established, PASSER's exit routine is scheduled with an NSPE or Notify RU.)	The SCIP exit routine is entered twice; once by the UNBIND received from PASSER, again by the BIND received from PLUAPPL.
Application program named GETTER issues SIMLOGON OPTCD=RELRQ requesting PLUAPPL to release an LU with which it is currently in session.	RELREQ exit routine is scheduled.	(Not applicable)
Note: If the program does not have the exit routine, no notification occurs, or the specified function is not supported.

Table 2. Summary of exit routines involved in session outages or disruption
Action or event causing session outage ¹ or session disruption	Method of notification
	…for application program acting as PLU ²	…for application program acting as SLU ²
Session outage occurs (for example, because of a link failure, a virtual route deactivation, an RU received exceeding maximum RU size, an NCP failure, or a switched line disconnection).	If SONSCIP=YES is coded on the PLU application program's APPL definition statement, UNBIND is received in the SCIP exit routine. If SONSCIP=NO and the application program has an NSEXIT exit routine, that exit routine is scheduled with CLEANUP. Otherwise, the LOSTERM exit routine is scheduled.	SCIP exit routine is scheduled with UNBIND or, depending on the type of outage, NSEXIT exit routine can be scheduled with CLEANUP.
VTAM operator issues a VARY NET,INACT,I (immediate) command to deactivate an LU in the same domain or to deactivate a resource representing an LU in another domain.	LOSTERM exit routine is scheduled.	UNBIND is received in the SCIP exit routine. If the normal communication paths are not available, NSEXIT exit routine is scheduled with CLEANUP.
VTAM operator issues a VARY NET,TERM,TYPE=UNCOND command to terminate one or more sessions.	LOSTERM exit routine is scheduled.	UNBIND is received in the SCIP exit routine. If normal communication paths are not available, NSEXIT exit routine is scheduled with CLEANUP.
VTAM operator issues a VARY NET,INACT,F or R command to deactivate an LU in the same domain or to deactivate a resource representing an LU in another domain.	If the application program has an NSEXIT exit routine, that exit routine is scheduled with CLEANUP. Otherwise, the LOSTERM exit routine is scheduled. ³	NSEXIT exit routine is scheduled with CLEANUP. For some race (contention) conditions, SCIP exit routine can be scheduled with UNBIND instead.
VTAM operator issues a VARY NET,TERM,TYPE=FORCE command to terminate one or more sessions.	If the application program has an NSEXIT exit routine, that exit routine is scheduled with CLEANUP. Otherwise, the LOSTERM exit routine is scheduled.	NSEXIT exit routine is scheduled with CLEANUP. For some race (contention) conditions, SCIP exit routine can be scheduled with UNBIND instead.
VTAM operator issues a VARY NET,TERM,TYPE=COND command to terminate one or more sessions.	LOSTERM exit routine is scheduled.	UNBIND is received in SCIP exit routine if PLU terminates session.
Session-type error detected (RUs discarded because of lack of buffer space).	LOSTERM exit routine is scheduled.	LOSTERM exit routine is scheduled.
One of the following situations occurs: VTAM is being terminated. VTAM recognizes an internal error. VTAM receives a HALT command or VARY NET,INACT command for the application program from the operator. An alternate application has issued an OPEN ACB to take over sessions from an application program that has enabled persistence.	TPEND exit routine is scheduled.	TPEND exit routine is scheduled.
Note: A session outage is any action or event that causes a path between a PLU and an SLU to break or that causes loss of one of the participants in the session. If the program does not have an applicable exit routine, notification does not occur. Certain error conditions are indicated only through a LOSTERM exit routine. Specify either exit routine, or both. If you do not specify either exit routine, the VARY INACT command hangs.

Table 3. Summary of exit routines involved in session termination by session participant
Action or event causing session termination	Method of notification
Action or event causing session termination	…for application program acting as PLU ¹	…for application program acting as SLU ¹
Device-type LU requests session termination (forced or orderly).	LOSTERM exit routine is scheduled. ²	(Not applicable)
Application program issues TERMSESS OPTCD=UNBIND.	SCIP exit routine with UNBIND. ² ³	(Not applicable)
Application program issues TERMSESS OPTCD=COND or UCOND.	LOSTERM exit routine is scheduled.	UNBIND received in SCIP exit routine.
Application program issues CLSDST.	(Not applicable)	UNBIND received in SCIP exit routine.
Application program acting as SLU issues CLOSE or device-type LU requests session termination (CLEANUP).	SCIP exit routine with UNBIND, NSEXIT exit routine with CLEANUP, or LOSTERM exit routine is scheduled.	(Not applicable)
Application program acting as PLU issues CLOSE.	(Not applicable)	SCIP exit routine with UNBIND or NSEXIT exit routine with CLEANUP is scheduled.
Note: If the program does not have the required exit routine, notification does not occur. For forced termination, if the normal communication paths are unavailable, the SCIP exit routine with UNBIND or NSEXIT exit routine with CLEANUP is scheduled. For the PLU's SCIP to be driven with an UNBIND, you must code SONSCIP=YES on the APPL definition statement.