      SPA subprocess  to  execute a command line, and to continue working in DCL.
 When the command completes, you will be notified (as with a batch  job)
 of the completion and status of the spawned command.
ith a batch  job)

f the completion and status of the spawned command.

2       The 
    The SPAWN command must obey the following syntax:
  
         $ SPAWN  {-options}  command-line

3 
Options
-n
<procname>        (set process name)
 G special characters, enclose the entire argument in quotes, as in:
  or

pecial characters, enclose the entire argument in quotes, as in:
  
         "-nProcess 1"
 I from  the  command  line,  or  from  the  user name if the command line
 results in an illegal process name.
the  user name if the command line

esults in an illegal process name.

-l
<logfile>         (set log file name)
 D is not given, the default log file is SYS$LOGIN:SPAWN.LOG.
his  option

s not given, the default log file is SYS$LOGIN:SPAWN.LOG.

-q
                   (quick spawn)
 S Saves start-up time for simple subprocesses.
  key  definitions,  etc.

aves start-up time for simple subprocesses.

3       Any v as  they  would  appear  if  executed  directly  from DCL, i. e. if the
 command contains special characters or spaces, enclose the  appropriate
 arguments in quotes.
al characters or spaces, enclose the  appropriate

rguments in quotes.
   which  the  user  has  added to his current process via the SET COMMAND
 command will NOT be passed to the spawned subprocess.
 the SET COMMAND

ommand will NOT be passed to the spawned subprocess.
   the  first line with an underscore ("_"), and SPAWN.COM will prompt you
 for additional lines.  Note that this is not the same as ending  a  DCL
 command  line with a hyphen ("-"), which causes that command line to be
 continued.
e with a hyphen ("-"), which causes that command line to be

ontinued.
2       Inv
    Invoke SPAWN by typing
  
         $ @SUP_COM:SPAWN ...
 Y
ou may if you wish define a command synonym to invoke SPAWN, such as:
  
         $ SPN :== @SUP_COM:SPAWN
 ( may not work correctly when called by other utilities expecting the DCL
 SPAWN command.)
ectly when called by other utilities expecting the DCL

PAWN command.)
2 
Examples
 1
)  Spawn a process to request a tape mount.
  
   $ SPAWN REQUEST/REPLY "Please mount tape # 1234 on MFA0:, ring in."


2       Any errors w executing  are  trapped  and  reported  to the user.  If the subprocess
 terminated normally, the message
rted  to the user.  If the subprocess

erminated normally, the message
  
         %SPAWNDONE-S-COMPLETE, Subprocess procname completed
 i errors  during  execution,  the  first  such error is reported with the
 following format:
cution,  the  first  such error is reported with the

ollowing format:
             -XYZ-X-ERRORNAME, Example of an error
ss procname

         -XYZ-X-ERRORNAME, Example of an error
 A
ny other errors which occur are counted and reported as follows:
  
         %SPAWNDONE-I-MORERRORS, n more error(s) detected in procname

2       SPAWN us
    SPAWN uses the following files:
 S      appropriate DCL commands to allow error processing.  "hhmmsscc" is
      the time-of-day computed by SPAWN when it begins.
  "hhmmsscc" is

    the time-of-day computed by SPAWN when it begins.
 S      generated  by the subprocess (if any).  They are combined into one
      error message file called -
(if any).  They are combined into one

    error message file called -
 S      of  their  generation.   "pid"  is  the  process ID string for the
      subprocess (NOT the user's pid!).
 the  process ID string for the

    subprocess (NOT the user's pid!).
 A subprocess exits correctly.
cleaned up by SPAWNDONE if  and  when  the
