LOSTERM exit routine

The LOSTERM exit routine is scheduled to inform the application program that one of the following events has occurred for a session with this application program:

Request/response units have been discarded because the application program would not accept them and there is no buffer space to queue them in VTAM®; session data recovery or session termination is required. This is the only reason that LOSTERM can be scheduled for an SLU application program.
A CTERM Conditional has been received by a PLU application program, perhaps because the other end of the session issued TERMSESS OPTCD=COND; the application program determines the appropriate response or action.
A CTERM Forced has been received by a PLU application program whose LOSTERM Exit has not already been scheduled for a CTERM conditional, perhaps because the other end of the session issued TERMSESS OPTCD=UNCOND; CLSDST is required for this session.
A Test Request message has been received from a BSC 3270 terminal; CLSDST is required for this session.
A session outage has occurred that normally would have been reported through the NSEXIT or SCIP exit routines, but these exit routines are not available. See Table 1 for a summary of session outage notification. CLSDST might be required for this session.
A request to suspend or resume a synchronous cross-memory SRB-mode macroinstruction request has been unsuccessful. The LOSTERM exit is used to notify the application program because normal request completion notification cannot be performed.

See Stages of session termination for further information about these exits.

The CID of the affected session is provided in the LOSTERM exit routine parameter list. The contents of the USERFLD field from the NIB used when the session is established are also provided. The exit parameter list contains a code indicating the reason the LOSTERM exit routine is scheduled.