Resumes execution of a suspended operation.
After a program or MPE/iX command operation is suspended by
pressing [Break] or by using the CAUSEBREAK intrinsic, the
RESUME command resumes execution of the operation at the
point where the execution was suspended. Note that the
RESUME command is legitimate only during a BREAK. Many MPE
XL commands are aborted rather than suspended by a BREAK,
and thus cannot be resumed. (Refer to Table 1-8 for a list
of nonbreakable commands.)
If, instead of RESUME, you enter another program command
(such as EDITOR, FTNXL, or RUN) or one of the nonprogram
commands (HELLO or BYE), the Command Interpreter prints
the following message on your terminal ABORT? (YES/NO).
If you respond YES to the ABORT? message, the Command
Interpreter aborts the current (suspended) program and
executes the command.
If you respond NO to the ABORT? message, the Command
Interpreter prints the message COMMAND NOT ALLOWED IN BREAK
and prompts you for another command. If you now enter
RESUME at the prompt, the suspended program continues at the
point where it was interrupted. If you had logged on using
the PARM= option of HELLO to create a process with ;PARM=1
(or 3), and then have the occasion to respond YES to an
ABORT? message, MPE/iX will abort the command process and
log you off immediately. This is similar to the action of
MPE V/E with the ()COMMAND LOGON command.
This command may be issued only while in BREAK. It may not
be used from a session (other than while in BREAK mode), job,
or program. Pressing [Break] has no effect on this command.
To continue a suspended program at the point of