Use STARTUP to add, modify, display and remove components for the
 STARTUP component files used when starting VAX/VMS during a system
 boot.  Use of this command requires access to the STARTUP database
 file.

Additional information available:

ADDCREATEREMOVEDISABLEENABLEMODIFYSET
SHOW

 Use the ADD command to add a component to the
 startup component database.

 Format:
   STARTUP ADD FILE filename

Additional information available:

filenameCommand QualifiersExamples

 Startup component filenames should include only a name and a
 file type. The file type should be .COM or .EXE.  The file
 should be located in SYS$STARTUP or SYS$MANAGER.  This requires
 READ and WRITE access to the STARTUP component database.

Additional information available:

/CONFIRM/LOG/MODE/NODE/PARAMETERS/PHASE

 /NOCONFIRM [Default]

 Specifies if the operation should be confirmed.  If /CONFIRM is
 specified you will be asked to confirm your request to add a new
 entry in the  component file.

 /NOLOG [Default]

 Determines if the ADD command echoes the name and phase of the
 component added to the component database.

 /MODE=execution-mode

 Specifies the mode that the component file should be executed in.
 Valid modes are DIRECT, SPAWN, BATCH, CALLED or ANY.

 /NODE=node_list

 Specifies the node(s) that the component file should be executed on.

 A node list is either a single node, LARRY, a list of nodes, like
 (LARRY, CURLY, MOE), or * meaning ALL nodes.

 /PARAMETERS=(Pn:[value],...)

 Specifies the parameters which are to be sent to the component
 file during startup.  Parameters which are omitted receive the
 default parameters defined by the STARTUP_Pn sysgen parameters.

 Specifying a parameter without a value will force that parameter
 to be empty during startup.

 /PHASE=phase_name

 Specifies the phase that the component file should be executed
 in. If omitted, the phase defaults to LPMAIN.

 SYSMAN> STARTUP ADD FILE MY_PRODUCT.COM

 Component file SYS$STARTUP:MY_PRODUCT.COM is added to the component
 database.  This file will execute in the LPMAIN phase in DIRECT mode,
 on all nodes in the cluster, and with the default parameter set.

 SYSMAN> STARTUP ADD FILE MY_PRODUCT.COM/PARAM=(P2,P3:TRUE)/PHASE=LPBETA

 Component file SYS$STARTUP:MY_PRODUCT.COM is added to the component
 database.  This file will execute in the LPBETA phase in DIRECT mode,
 on all nodes in the cluster, with parameter 2 (P2) set blank, P3 set
 to TRUE, and P1, P4, P5, etc. set to their default values.

 Creates a new, empty startup component database.  This component
 database will supersede the current component database of the same
 name, if any.

 Format:
   STARTUP CREATE [component-database]

Additional information available:

component-databaseCommand qualifiersExamples

 A VAX/VMS file specification.  The device/directory specification
 should be either SYS$STARTUP or SYS$MANAGER.  If a component
 database is named, an empty file with that name will be created
 and will become the current data file (see SET/SHOW DATABASE).
 If no component database is named, the current component database
 name will be used.  At a minimum, READ access to the named file
 is required.

Additional information available:

/CONFIRM

 /NOCONFIRM

 Specifies if the operation should be confirmed.  The default is
 yes, meaning you will be asked to confirm your request before
 the component database is created.

 SYSMAN> STARTUP CREATE SYS$STARTUP:N.DAT
 do you wish to create a new component database SYS$STARTUP:N.DAT? [N]:>Y
 %SYSMAN-I-NEWCOMPFIL, current component database is now SYS$STARTUP:N.DAT

 This dialogue shows the creation of a new component database named
 SYS$STARTUP:N.DAT.  Subsequent STARTUP command will affect this
 data file.  READ and WRITE access to this file is required.

 Deletes one or more component files from the STARTUP component database.
 Requires WRITE access to the component database.

 Format:
   STARTUP REMOVE FILE component-name

Additional information available:

component-nameCommand Qualifiers

 Specifies the component file(s) you are interested in.  You
 should specify only a file name and a file type.  Wildcard
 characters (% and *) may be used freely.

Additional information available:

/CONFIRM/LOG/PHASE

 /NOCONFIRM

 Controls whether a request is issued before each individual
 REMOVE operation to confirm that the operation should be
 performed on that file.

 /NOLOG [D]

 Determines if the REMOVE command displays the names of the
 components removed from the component database.

 /PHASE=phase

 Selects all components within a specified phase.

 Disables a component file so that it is not executed.

 Format:
   STARTUP DISABLE FILE component-file

Additional information available:

component-fileCommand Qualifiers

 Specified the file(s) you are interested in.  You should specify
 only a file name and a file type.  Wildcard characters (% and *)
 may be used freely.

Additional information available:

/LOG/PHASE/NODE

 /NOLOG [default]

 Determines if the DISABLE command displays the names of the
 components which are disabled.

 /PHASE=phase

 Selects all components within a specified phase that match
 'component-file'.

 /NODE=node-list

 Selects which node(s) the component file is NOT to be executed
 on. If this qualifier is omitted, the component file is not
 executed on any nodes.

 'node_list' is either a single node, LARRY, a list of nodes,
 like (LARRY, CURLY, MOE), or * meaning ALL nodes.

 Enables a component file so that it is executed during system startup.

 Format:
   STARTUP ENABLE FILE component-file

Additional information available:

component-fileCommand Qualifiers

 Specified the file(s) you are interested in.  You should specify
 only a file name and a file type.  Wildcard characters (% and *)
 may be used freely.

Additional information available:

/LOG/PHASE/NODE

 /NOLOG [default]

 Determines if the ENABLE command displays the names of the
 components which are enabled.

 /PHASE=phase

 Selects all components within a specified phase.

 /NODE=node-list

 Selects which node(s) the component file is to be executed on.
 If this qualifier is omitted, the component file is executed on
 all nodes.

 A node-list is either a single node, LARRY, a list of nodes,
 like (LARRY, CURLY, MOE), or * meaning ALL nodes.

 Changes some or all of the information about one or more
 component files within the startup component database.
 Requires WRITE access to the startup component database.

 Format:
    STARTUP MODIFY FILE component-file

Additional information available:

component-fileCommand Qualifiers

 Specified the file(s) you are interested in.  You should specify
 only a file name and a file type.  Wildcard characters (% and *)
 may be used freely.

Additional information available:

/CONFIRM/LOG/MODE/NAME/PHASE

 /NOCONFIRM [D]

 Specifies if the operation should be confirmed.  If /CONFIRM is
 specified you will be asked to confirm your request to modify an
 entry in the component database.

 /NOLOG [D]

 Determines if the ADD command echoes the name and phase of the component
 added to the component database.

 /MODE=execution-mode

 Specifies the mode that the component file should be executed in.
 Valid modes are DIRECT, SPAWN, BATCH, CALLED or ANY.

 /NAME=component-name

 Specifies the new filename for the component file.

 /PHASE=phase-name

 Specified the phase that the component file is to be executed in.

 Sets various defaults for the user.

Additional information available:

DATABASE

 Specifies the name of the STARTUP component database to be used.

 Format:
    STARTUP SET DATABASE file-name

 Displays the name or contents of the current startup component database.

Additional information available:

DATABASEFILE

 Shows the name of the current STARTUP component database.

 Format:
   STARTUP SHOW DATABASE

Additional information available:

Command Qualifiers

Additional information available:

/OUTPUT

 /OUTPUT[=file-spec]

 Specifies that the output from the execution of this command is to
 written to the file specified, or to "[default_directory]SYSMAN.LIS"
 if no filespec is given.

 Shows one or more component file(s) from the component database.
 Requires READ access to the component database.

 Format:
   STARTUP SHOW FILE component-file

Additional information available:

component-fileCommand QualifiersExamples

 Specifies the component file(s) you are interested in.  You
 should specify only a file name and a file type.  Wildcard
 characters (% and *) may be used freely.

Additional information available:

/FULL/NODE/OUTPUT/PARAMETERS/PHASE

 Gives a more complete display, including the list of nodes that
 each component file is enabled or disabled on and the list of
 parameters which will be sent to the file during startup.

 Displays the list of node(s) on which the component file is
 enabled or disabled.

 /OUTPUT[=file-spec]

 Specifies that the output from the execution of this command is to
 written to the file specified, or to "[default_directory]SYSMAN.LIS"
 if no filespec is given.

 Displays the list of parameters which will be sent to the
 component file during startup.

 /PHASE=phase-name

 Displays information about all components within a specified phase.

 SYSMAN> STARTUP SHOW FILE

 Shows the name, phase name, and mode of execution for every
 component file in the current component database.

 SYSMAN> STARTUP SHOW FILE/PHASE=LPMAIN/NODE

 Shows the name, phase name, mode of execution and list of
 enabled/disabled nodes for every component file in phase LPMAIN
 in the current component database.

 SYSMAN> STARTUP SHOW FILE/PHASE=LPBEGIN/PARAM *.EXE

 Shows the name, phase name, mode of execution and list of parameters
 for every component file in phase LPMAIN with a file-type of .EXE.