DEBUG SPAWN — VMS C_3.0
Enables you to execute DCL commands without leaving the debugging
session. If you specify a DCL command as the parameter to SPAWN,
the command is executed in the context of a spawned subprocess.
For example, the command SPAWN MAIL invokes the VMS MAIL utility
and, when you exit from MAIL, you return to your debugging
session. If you do not specify a parameter, the SPAWN command
brings you to DCL level in the spawned subprocess. You can then
enter DCL commands, and you return to your debugging session by
logging out of the subprocess.
Format:
SPAWN [/qualifier]
SPAWN dcl-command
SPAWN "dcl-command"
Additional information available:
Parameters
dcl-command
Can be any dcl-command. If the command contains a semicolon,
then the entire command must be placed inside quotes so that the
debugger does not interpret the semicolon as the end of a
debugger command.
Example
DBG> SPAWN MAIL
You have 2 new messages
MAIL> ...
MAIL> EXIT
%DEBUG-I-RETURNED, control returned to process TITLE
DBG>
Qualifiers
Additional information available:
/INPUT=file-spec
Specifies an input file containing one or more DCL commands to be
executed by the spawned subprocess. If you specify a dcl-command
string with the SPAWN command and an input file with the /INPUT
qualifier, the dcl-command string is processed before the input
file. Once processing of the input file is complete, the
subprocess is terminated.
No wildcards are allowed in the file specification.
/NOWAIT
Specifies that the parent process continue in parallel with the
spawned subprocess. This is the same as SPAWN/NOWAIT in DCL.
/OUTPUT=file-spec
Requests that the output from the SPAWN operation be written to
the specified file.
No wildcards are allowed in the file specification.
/WAIT
Specifies that the parent process should be suspended and that
the terminal should be attached to the sub-process.