SDISC Assembler Call - NetEx

Terminating a SessionNETEX sessions can terminate either normally or abnormally. A normal termination is planned by the programsinvolved. An abnormal termination is any unplanned termination of the session.Normal TerminationThis figure shows the exchange of session calls associated with normal (planned) termination. The steps arenumbered to simplify the discussion and do not necessarily represent the exact order which the events occur.Figure 9. Normal Session TerminationThe following numbered items refer to the steps in the figure above.1. Program A has a previously issued SREAD pending.2. Program B issues an SCLOSE. The SCLOSE takes the same form as an SWRITE request.3. Program B checks the NRB to verify that the SCLOSE was accepted by NETEX. If it was accepted, programB may close output files or perform other termination processing. No other NETEX write-type requests(except SDISCONNECT) may be issued by program B during this session. If the SCLOSE is notaccepted, Program B must act appropriately (check if NETEX is down or if the other application is notthere).4. Program B issues an SREAD. Program A may still write data to program B, or program A may issue anSCLOSE or an SDISCONNECT to terminate the session.5. Program A detects the SCLOSE.6. Program A issues an SCLOSE to terminate the session. Data may be associated with this request. ProgramA may issue any number of SWRITE requests before the SCLOSE.Page 20 Intertask Communication MAN-REF-H307IP-04