 |
HP OpenVMS System Management Utilities Reference
Manual
This example shuts down the local node in 2 hours. As long as you set
the environment to the local node, a subprocess of the SMISERVER system
detached process runs shutdown, and remaining logged into the system
during the shutdown is not necessary. If you do not set the environment
to the local node, the shutdown runs via a subprocess of the current
process, requiring that you remain logged in during the shutdown cycle.
SPAWN
Creates a subprocess of the current process. The context of the
subprocess is copied from the current process. You can use the SPAWN
command to leave SYSMAN temporarily, perform other tasks (such as
displaying a directory listing or printing a file), and return to
SYSMAN.
Note that SPAWN performs actions on the local node only. If you want to
execute DCL commands or command procedures throughout your environment,
use the DO command.
Requires TMPMBX or PRMMBX user privilege. The SPAWN command does not
manage terminal characteristics. You cannot use the SPAWN and ATTACH
commands if your terminal has an associated mailbox.
Format
SPAWN [command-string]
Parameter
command-string
Specifies a command string of fewer than 132 characters that you want
executed in the context of the created subprocess. When the command
completes execution, the subprocess terminates and control returns to
the parent process. If you specify both a command string and the /INPUT
qualifier, the command string executes before additional commands are
obtained from the /INPUT qualifier.
Qualifiers
/INPUT=filespec
Specifies an input file containing one or more DCL command strings that
you want executed by the spawned subprocess. If you specify a command
string along with an input file, the command string gets processed
before the commands in the input file. When processing is complete, the
subprocess terminates.
/LOGICAL_NAMES (default)
/NOLOGICAL_NAMES
Specifies that the logical names of the parent process are copied to
the subprocess. When you do not want the subprocess to use the logical
names of the parent process, enter the /NOLOGICAL_NAMES qualifier.
/OUTPUT=filespec
Identifies the output file to which the results of the operation are
written. Specify an output other than SYS$OUTPUT whenever you use the
/NOWAIT qualifier. This prevents output from being displayed while you
are specifying new commands. If you omit the /OUTPUT qualifier, output
gets written to the current SYS$OUTPUT device.
/PROCESS=subprocess-name
Specifies the name of the subprocess that you want to create. The
default subprocess name is in the format USERNAME_n.
/SYMBOLS (default)
/NOSYMBOLS
Determines whether the system passes DCL global and local symbols to
the subprocess.
/WAIT (default)
/NOWAIT
Controls whether the system waits until the subprocess completes before
you can specify more commands. The /NOWAIT qualifier enables you to
specify new commands while the specified subprocess is running. If you
specify the /NOWAIT qualifier, use the /OUTPUT qualifier to direct the
output to a file instead of displaying it on the screen. Doing this
prevents your terminal from being used by more than one process
simultaneously.
Description
The SPAWN command creates a subprocess of your current process with the
following attributes copied from the parent process:
- All symbols except $RESTART, $SEVERITY, and $STATUS
- Key definitions
- The current keypad state
- The current prompt string
- All process logical names and logical name tables except those
explicitly marked CONFINE or those created in executive or kernel mode
- Default disk and directory
- Current SET MESSAGE settings
- Current process privileges
- Control and verification states
Note that some attributes, such as the process's current command
tables, are not copied.
When the subprocess is created, the process-permanent open files and
any image or procedure context are not copied from the parent process.
The subprocess is set to command level 0 (DCL level with the current
prompt).
If you do not specify the /PROCESS qualifier, the name of this
subprocess is composed of the same base name as the parent process and
a unique number. For example, if the parent process name is SMITH, the
subprocess name can be SMITH_1, SMITH_2, and so on.
The LOGIN.COM file of the parent process is not executed for the
subprocess because the context is copied separately, allowing quicker
initialization of the subprocess. When the /WAIT qualifier is in
effect, the parent process remains in hibernation until the subprocess
terminates or returns control to the parent by way of the ATTACH
command.
More than one process simultaneously attempts to use the same input or
output stream when several processes share that stream and you perform
one of the following actions:
- Terminate a subprocess to which you are not currently attached.
- Terminate a process that is not spawned from the process to which
you are currently attached.
Use the LOGOUT command to terminate the subprocess and return to the
parent process. You can also use the ATTACH command (see ATTACH) to
transfer control of the terminal to another process in the subprocess
tree, including the parent process. (The SHOW PROCESS/SUBPROCESSES
command displays the processes in the subprocess tree and points to the
current process.)
Note
Because a tree of subprocesses can be established using the SPAWN
command, you must be careful when terminating any process in the tree.
When a process is terminated, all subprocesses below that point in the
tree are automatically terminated.
|
Qualifiers used with the SPAWN command must directly follow the command
verb. The command string parameter begins after the last qualifier and
continues to the end of the command line.
Examples
| #1 |
SYSMAN> SPAWN DIR SYS$MANAGER:SITE*.*
Directory CLU$COMMON:[SYSMGR]
SITE$STARTUP.COM;5
Total of 1 file.
SYSMAN>
|
This command enables you to enter the DIRECTORY command in DCL to see
if a site-specific startup file is in the directory. After the
DIRECTORY command executes, control returns to the parent process.
| #2 |
SYSMAN> SPAWN
$ EDIT SITE$STARTUP.COM
.
.
.
$ LOGOUT
Process SYSTEM_1 logged out at 28-JUN-2002 10:05:17.24
SYSMAN>
|
This example shows how you can use the SPAWN command to leave SYSMAN
and edit a file. The LOGOUT command returns you to SYSMAN.
| #3 |
SYSMAN> SPAWN /NOLOGICAL_NAMES SET HOST
_Node: NODE21
.
.
.
$ LOGOUT
%REM-S-END, control returned to node _NODE22::
SPAWN>
|
This example shows how you can use the SPAWN command to create a
subprocess in which you can use the SET HOST command. When you want to
leave NODE21, enter the LOGOUT command. The /NOLOGICAL_NAMES qualifier
prevents the logical names of the parent process from being copied to
the subprocess.
STARTUP ADD
Adds a component to the startup database.
Requires read (R) and write (W) access to the startup database.
Format
STARTUP ADD FILE filespec
Parameters
FILE
Adds a component to the startup database. SYSMAN modifies
STARTUP$STARTUP_LAYERED by default.
filespec
Specifies which file to add to the startup database. Each component of
the startup database must have a file type of .COM or .EXE and reside
in SYS$STARTUP.
Qualifiers
/CONFIRM
/NOCONFIRM (default)
Controls whether SYSMAN displays the file specification of each file
before adding it to the startup database and requests you to confirm
the addition. If you specify /CONFIRM, you must respond to the prompt
with a Y (Yes) or a T (True) and press Return before the file is added.
If you enter anything else, such as N or No, the requested file is not
added.
/LOG
/NOLOG (default)
Controls whether the STARTUP ADD command displays the file
specification of each file after it has been added.
/MODE=mode
Specifies the mode of execution for the file. Valid modes include
DIRECT, SPAWN, BATCH, or ANY, as described in the HP OpenVMS System Manager's Manual.
/NODE=(node1,node2,...,noden)
Names the nodes within the cluster that run the file during startup. By
default, a startup file executes on all nodes in the cluster.
/PARAMETER=(P1:arg1,P2:arg2,...,P8:arg8)
Specifies the parameters that are to be passed to the file during
startup. Parameters that are omitted receive the default parameters
defined by the system parameter STARTUP_Pn. If STARTUP_Pn is blank,
"FULL" is used as parameter 1 (P1) and is passed by STARTUP.COM to each
startup component file. If you want a blank P1 parameter given to a
specific component file, use the command:
SYSMAN> STARTUP MODIFY FILE component.com/PARAM=P1:""
|
/PHASE=phase-name
Indicates the phase within system startup when the file is to be
executed. Valid phases include LPBEGIN, LPMAIN, LPBETA, and END. LPMAIN
is the default.
Description
The STARTUP ADD command adds a component to the startup database.
Startup components are the command procedures or executable files that
perform actual startup work. Files from the startup database are used
to start the operating system, site-specific programs, and layered
products. STARTUP$STARTUP_VMS and STARTUP$STARTUP_LAYERED list the
components of the startup database.
Because an OpenVMS Cluster typically shares one copy of the startup
database, the SYSMAN environment can be defined as clustered or as a
single node within the cluster.
Example
|
SYSMAN> STARTUP ADD FILE /MODE=DIRECT /PHASE=LPMAIN -
_SYSMAN> DECSET$ENVMGR_STARTUP.COM
|
This command adds a record to the startup database that starts the
DECSET environment manager software.
STARTUP DISABLE
Prevents a file in the startup database from executing.
Requires read (R) and write (W) access to the startup database.
Format
STARTUP DISABLE FILE filespec
Parameters
FILE
Disables a component of the startup database. SYSMAN modifies
STARTUP$STARTUP_LAYERED by default.
filespec
Specifies the name of a component in the startup database. The startup
file must reside in SYS$STARTUP and have a file type of .COM or .EXE.
The asterisk (*) and percent (%) wildcard characters are permitted.
Qualifiers
/CONFIRM
/NOCONFIRM (default)
Controls whether the STARTUP DISABLE command displays the file
specification of each file before disabling it in the startup database
and requests you to confirm that the file be disabled. If you specify
/CONFIRM, you must respond to the prompt with a Y (Yes) or a T (True)
and press Return before the file is disabled. If you enter anything
else, such as N or No, the requested file is not disabled.
/LOG
/NOLOG (default)
Controls whether the STARTUP DISABLE command displays the file
specification of each file after it has been disabled.
/NODE=(node1,node2,...,noden)
Identifies nodes within the cluster that do not run the file during
startup. By default, the startup file is disabled on all nodes in the
cluster.
/PHASE=phase-name
Indicates the phase of system startup in which the specified file
normally executes. Valid phases include LPBEGIN, LPMAIN, LPBETA, and
END. LPMAIN is the default.
Description
The STARTUP DISABLE command prevents a file in the startup database
from executing. The command edits a record in the startup database,
temporarily disabling the file.
Example
|
SYSMAN> STARTUP DISABLE FILE /NODE=NODE21 DECSET$ENVMGR_STARTUP.COM
|
This command modifies the startup database so that the DECset
environment manager will not be installed on NODE21.
STARTUP ENABLE
Enables a previously disabled file in the startup database to execute
during system startup.
Requires read (R) and write (W) access to the startup database.
Format
STARTUP ENABLE FILE filespec
Parameters
FILE
Enables a component of the startup database. SYSMAN modifies
STARTUP$STARTUP_LAYERED by default.
filespec
Specifies the name of the startup file that you are enabling. Wildcard
characters are accepted.
Qualifiers
/CONFIRM
/NOCONFIRM (default)
Controls whether the STARTUP ENABLE command displays the file
specification of each file before enabling it in the startup database
and requests you to confirm that the file be enabled. If you specify
/CONFIRM, you must respond to the prompt with a Y (Yes) or a T (True)
and press Return before the file is enabled. If you enter anything
else, such as N or No, the requested file is not enabled.
/LOG
/NOLOG (default)
Controls whether the STARTUP ENABLE command displays the file
specification of each file after it has been enabled.
/NODE=(node1,node2,...,noden)
Names nodes within the cluster where the file will be enabled. By
default, the startup file is enabled on all nodes.
/PHASE=phase-name
Indicates the phase within system startup when the specified file is to
be enabled. Valid phases include LPBEGIN, LPMAIN, LPBETA, and END.
LPMAIN is the default.
Description
The STARTUP ENABLE command permits a file that was previously disabled
to execute during system startup.
Example
|
SYSMAN> STARTUP ENABLE FILE /NODE=NODE22 DECSET$ENVMGR_STARTUP.COM
|
This command modifies the startup database. NODE22 will have the DECSET
environment manager installed at startup.
STARTUP MODIFY
Changes information associated with a startup file in the startup
database.
Requires read (R) and write (W) access to the startup database.
Format
STARTUP MODIFY FILE filespec
Parameters
FILE
Modifies a record in the startup database. SYSMAN modifies
STARTUP$STARTUP_LAYERED by default.
filespec
Selects a startup file for modification. Wildcard characters are
accepted.
Qualifiers
/CONFIRM
/NOCONFIRM (default)
Controls whether the STARTUP MODIFY command displays the file
specification of each file before modifying its startup characteristics
in the startup data file and requests you to confirm that the file
characteristics be modified. If you specify /CONFIRM, you must respond
to the prompt with a Y (Yes) or a T (True) and press Return before the
file is modified. If you enter anything else, such as N or No, the
requested file is not modified.
/LOG
NOLOG (default)
Controls whether the STARTUP MODIFY command displays the file
specification of each file after its startup characteristics have been
modified.
/MODE=mode
Changes the mode of execution for a startup file. Valid modes include
DIRECT, SPAWN, BATCH, or ANY, as described in the HP OpenVMS System Manager's Manual.
/NAME=filespec
Changes the name of the startup file. The file must reside in
SYS$STARTUP.
/PARAMETER=(P1:arg1,P2:arg2,...,P8:arg8)
Changes the parameters that are to be passed to the file during
startup. Parameters that are omitted receive the default parameters
defined by the system parameter STARTUP_Pn. If STARTUP_Pn is blank,
"FULL" is used as parameter 1 (P1) and is passed by STARTUP.COM to each
startup component file. If you want a blank P1 parameter given to a
specific component file, use the command:
SYSMAN> STARTUP MODIFY FILE component.com/PARAM=P1:""
|
/PHASE=phase-name
Selects startup files for modification based on the phase in which they
run. Valid phases include LPBEGIN, LPMAIN, LPBETA, and END. LPMAIN is
the default.
Description
The STARTUP MODIFY command edits startup information associated with
components in the startup database. For example, the command can rename
a file or change the parameters that are passed to a file during
startup. You can select a group of files for modification based on the
phase in which they run.
Example
|
SYSMAN> STARTUP MODIFY FILE DECSET$ENVMGR_STARTUP.COM -
_SYSMAN> /PARAM=(P3:TRUE,P4:FALSE) /CONFIRM
|
This command changes two startup parameters for the command procedure
DECSET$ENVMGR_STARTUP.COM.
STARTUP REMOVE
Removes a record in the startup database, so the specified startup file
no longer executes during system startup.
Requires read (R) and write (W) access to the startup database.
Format
STARTUP REMOVE FILE filespec
Parameters
FILE
Removes a component from the startup database. SYSMAN modifies
STARTUP$STARTUP_LAYERED by default.
filespec
Specifies the name of the file to remove from the startup database.
Wildcard characters are accepted.
Qualifiers
/CONFIRM
/NOCONFIRM (default)
Controls whether the STARTUP REMOVE command displays the file
specification of each file before deleting its record in the startup
database and requests you to confirm that the file be deleted. If you
specify /CONFIRM, you must respond to the prompt with a Y (Yes) or a T
(True) and press Return before the file is removed. If you enter
anything else, such as N or No, the requested file is not removed.
/LOG
/NOLOG (default)
Controls whether SYSMAN displays the file specification of each file
after it has been removed.
/PHASE=phase-name
Indicates the phase of system startup from which the file will be
removed. Valid phases include LPBEGIN, LPMAIN, LPBETA, and END.
Example
|
SYSMAN> STARTUP REMOVE FILE DECSET$ENVMGR_STARTUP.COM /LOG
|
This command takes the file DECSET$ENVMGR_STARTUP.COM out of the
startup database.
STARTUP SET DATABASE
Establishes the current startup database.
Format
STARTUP SET DATABASE database
Parameter
database
Specifies the name of the target database, which is
STARTUP$STARTUP_LAYERED by default. The second database,
STARTUP$STARTUP_VMS, is available for viewing; however, HP recommends
that you do not modify it.
Qualifiers
None.
Example
|
SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_LAYERED
%SYSMAN-I-NEWCOMPFIL, current component file is now STARTUP$STARTUP_LAYERED
SYSMAN> STARTUP SHOW FILE
%SYSMAN-I-COMPFIL, contents of component database on node LUCERN
Phase Mode File
----- ---- ---------------------------
LPBEGIN DIRECT VMS$LPBEGIN_070_STARTUP.COM
LPMAIN DIRECT FOR$LPMAIN_070_STARTUP.COM
|
The commands in this example establish the layered products database as
the default, so it can be displayed.
STARTUP SET OPTIONS
Controls logging and display of information for one or more nodes in a
cluster during startup.
Requires READ (R) and WRITE (W) access to the current system parameter
file on disk: SYS$SYSTEM:ALPHAVMSSYS.PAR (for Alpha), and
SYS$SYSTEM:IA64VMSSYS.PAR (for Integrity servers).
Format
STARTUP SET OPTIONS
Parameters
None.
Qualifiers
/CHECKPOINTING
/NOCHECKPOINTING
Displays informational messages describing the time and status of each
startup phase and component procedure.
The value of the system parameter STARTUP_P2 that corresponds to
/OUTPUT=CHECKPOINTING is "C".
/OUTPUT=FILE,CONSOLE
Sends output generated by using the /VERIFY qualifier to a file or to
the system console. If you choose the FILE option, it creates
SYS$SPECIFIC:[SYSEXE]STARTUP.LOG.
The value of the system parameter STARTUP_P2 that corresponds to
/OUTPUT=FILE is "D".
/VERIFY=FULL,PARTIAL
/NOVERIFY
Displays startup procedures as they execute. This qualifier defines the
system parameter STARTUP_P2 to have the appropriate value based on the
options you choose. (/VERIFY with no value following it is the
equivalent of /VERIFY=full.)
/VERIFY options are in the following table:
| Value |
Description |
|
FULL
|
Displays every line of DCL executed by startup component procedures and
by STARTUP.COM.
The value of the system parameter STARTUP_P2 that corresponds to
this option is "V".
|
|
PARTIAL
|
Displays every line of DCL executed by startup component procedures,
but does not display DCL executed by STARTUP.COM.
The value of the system parameter STARTUP_P2 that corresponds to
this option is "P".
|
Caution
All STARTUP_P2 parameter values modified by the SYSMAN STARTUP OPTIONS
will be overridden by the AUTOGEN command procedure. To preserve any
parameter modifications made with SYSMAN, edit the
SYS$SYSTEM:MODPARAMS.DAT file, as explained in the HP OpenVMS System Manager's Manual.
|
Description
The STARTUP SET OPTIONS command enables you to control logging and
checkpointing during startup. You can control the amount of information
logged (full or partial) and where it is displayed (file or console).
You can also choose checkpointing, which displays informational
messages about the time and status of each phase during startup.
The default options are /NOCHECKPOINTING, /OUTPUT=CONSOLE, and
/NOVERIFY.
Because SYSMAN enables you to define the target environment, you can
perform startup logging on your local node, your own cluster, and a
subset of nodes on your cluster. See the SET ENVIRONMENT command for
more information.
Example
|
SYSMAN> STARTUP SET OPTIONS/VERIFY=FULL/OUTPUT=FILE/CHECKPOINTING
|
This example requests startup logging with full verification, output to
SYS$SPECIFIC:[SYSEXE]STARTUP.LOG, and checkpointing. The corresponding
value for system parameter STARTUP_P2 is "VDC".
|
