In both F mode and L mode, the EDT session can be interrupted by means of @SYSTEM or by pressing [K2]. In both cases EDT remains loaded.
If, during the period of interruption, other programs are loaded via the BS2000 command interface (e.g. with /START-PROGRAM or /LOAD-PROGRAM) or if procedures are started which load other programs then EDT is unloaded without any query being issued and it is then not possible to continue the EDT session.
It is possible to return to the interrupted EDT work mode using the /RESUME-PROGRAM command. The /RESUME-PROGRAM command continues the EDT session at the point where it was interrupted.
In F mode, if the work window in which the EDT session was interrupted is not displayed or is incomplete following /RESUME-PROGRAM, then the original content can be restored by pressing [K3]. If EDT is interrupted using [K2] then all input which has not yet been transferred is lost.
It is also possible to continue an interrupted EDT session mode using the /INFORM-PROGRAM command. When this is done, any message passed in the command is ignored.
If the @SYSTEM statement was specified in a statement sequence in F mode or in an input block in L mode (BLOCK mode) and /INFORM-PROGRAM is used to return to EDT after the interruption then a message is output and the remainder of the statement line or input block after @SYSTEM is not executed.
If, at the time of interruption, EDT had not yet fully processed the lines in a @DO or @INPUT procedure then the interrupted processing is aborted following a return with /INFORM-PROGRAM. A message is output and the remaining lines are not executed.
If a line range is being executed in an EDT statement at the time of interruption then execution of the statement is usually aborted and a message output on return to EDT with /INFORM-PROGRAM.
Note
The EDT run cannot be interrupted if EDT was started within a BS2000 system procedure protected against interruption by means of the setting INTERRUPT-ALLOWED=NO (see section “Access protection”).