Previous | Contents | Index |
On Alpha and Integrity servers, removes a reserved memory entry from the Reserved Memory Registry data file. This command takes effect on the next reboot and does not affect the running systems.
RESERVED_MEMORY REMOVE name
name
Name associated with the entry being removed. You must specify a name.If page tables are reserved for the named memory-resident global section, the additional reserved memory is also removed.
/GLOBAL_SECTION (default)
/NOGLOBAL_SECTION
/NOGLOBAL_SECTION indicates that the memory qualifier is for a privileged application instead of a group or system global section. (/GLOBAL_SECTION indicates that the memory qualifier is for a group or system global section.) You cannot use /NOGLOBAL_SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES./GROUP=n
You must specify /GROUP if the memory-resident global section is a group global section. Do not specify /GROUP if the memory-resident global section is a system global section. The value n is the UIC group number (in octal) associated with the memory-resident section being removed. You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION parameters./SYSGBL
Indicates that a reservation is for a system global memory resident section.You cannot combine this qualifier with the /GROUP or /NOGLOBAL_SECTION qualifier. This qualifier is the default unless you specify /GROUP or /NOGLOBAL_SECTION.
SYSMAN> RESERVED_MEMORY ADD DFW$GS1/SIZE=1 SYSMAN> RESERVED_MEMORY REMOVE DFW$GS1 |
The first command in this example adds DFW$GS1; the second command removes it.
On Alpha and Integrity servers, displays the memory reservations on the running system.The display includes how much of the reserved memory is currently in use by the named global section. It also includes how much memory is reserved and currently in use for page tables, if any, and the blocks of physical pages reserved.
RESERVED_MEMORY SHOW name
name
Name associated with the entry being displayed within the running system. If you do not specify a name, the system displays the reserved memory for all registered global sections.
/GLOBAL_SECTION (default)
/NOGLOBAL_SECTION
/NOGLOBAL_SECTION indicates that the memory qualifier is for a privileged application instead of a group or system global section. (/GLOBAL_SECTION indicates that the memory qualifier is for a group or system global section.) You cannot use /NOGLOBAL_SECTION with the qualifiers /GROUP, /SYSGBL, or /PAGE_TABLES./GROUP=n
You must specify /GROUP if the memory-resident global section is a group global section. Do not specify /GROUP if the memory-resident global section is a system global section. The value n is the UIC group number (in octal) associated with the memory-resident section being displayed. You can use the /GROUP qualifier only if you specify name. You cannot use the /GROUP qualifier with either /SYSGBL or /NOGLOBAL_SECTION parameters./SYSGBL
Indicates that a reservation is for a system global memory resident section.You cannot combine this qualifier with the /GROUP or /NOGLOBAL_SECTION qualifier. This qualifier is the default unless you specify /GROUP or /NOGLOBAL_SECTION.
SYSMAN> RESERVED_MEMORY SHOW %SYSMAN-I-OUTPUT, command execution on node PIPER Name Pages In Use Group PTs Alloced Zeroed DFW$GS_3 384 0 SYSGBL No No No DFW$GS_2 256 0 SYSGBL No Yes Yes DFW$GS_1 128 0 00000100 No No No DFW$GS_3 1 0 SYSGBL Yes No No DFW$GS_2 1 0 SYSGBL Yes Yes No |
The command in this example displays the memory reservations on a running system.
Defines the nodes or cluster to which subsequent commands apply.Requires OPER or SETPRV privilege on all nodes in the target environment.
SET ENVIRONMENT
None.
/CLUSTER
Specifies that all subsequent commands apply to all nodes in the cluster. By default, the management environment is the local cluster. Specify a nonlocal cluster by naming one cluster member with the /NODE qualifier./NODE=(node1,node2,...)
Specifies that SYSMAN execute subsequent commands on the given DECnet nodes. If accompanied by the /CLUSTER qualifier, the environment becomes the cluster where the given DECnet node is a member. A node name can be a system name, cluster alias, or logical name. However, before you can use logical names to define the command environment, you must set up the logical name table SYSMAN$NODE_TABLE. For more information about defining the SYSMAN logical name table, see the HP OpenVMS System Manager's Manual./USERNAME=username
Specifies that this user name should be used for access control purposes on another node. You can use this qualifier only in conjunction with the /CLUSTER or /NODE qualifiers. SYSMAN uses the current user name if none is supplied. SYSMAN prompts for a password whenever you specify a new user name.
Note
The account specified must have only a primary password. Accounts with secondary passwords are not supported.
The SET ENVIRONMENT command defines the target nodes or cluster for subsequent commands. When invoked, the system management environment is the local node where you are running SYSMAN. You can change the environment to any other nodes in the cluster, the entire cluster, or any nodes or cluster available through DECnet.Designate an OpenVMS Cluster environment with the /CLUSTER qualifier. When specifying a nonlocal cluster, also include the /NODE qualifier to identify the cluster.
If your environment consists of Vax, Alpha, and Integrity server nodes, see the DO command for information about creating logicals to manage each platform as an environment.
You can display the current environment with the command SHOW ENVIRONMENT. To adjust privileges and defaults for the current environment, use the SET PROFILE command.
An environment exists until you exit from SYSMAN or establish another command context with the SET ENVIRONMENT command.
#1 |
---|
SYSMAN> SET ENVIRONMENT/CLUSTER %SYSMAN-I-ENV, Current command environment: Clusterwide on local cluster Username ALEXIS will be used on nonlocal nodes |
This command defines the command environment as the local cluster. SYSMAN confirms the new environment.
#2 |
---|
SYSMAN> SET ENVIRONMENT/NODE=NODE21/CLUSTER Remote Password: %SYSMAN-I-ENV, Current command environment: Clusterwide on remote node NODE21 Username ALEXIS will be used on nonlocal nodes |
This command establishes a management environment on the cluster where NODE21 is a member. SYSMAN prompts for a password because it is a nonlocal environment.
#3 |
---|
SYSMAN> SET ENVIRONMENT/NODE=(NODE21,NODE22,NODE23) %SYSMAN-I-ENV, Current command environment: Individual nodes: NODE21,NODE22,NODE23 Username ALEXIS will be used on nonlocal nodes |
This command defines the management environment to be three individual nodes.
#4 |
---|
$ CREATE/NAME_TABLE/PARENT=LNM$SYSTEM_DIRECTORY - _$ SYSMAN$NODE_TABLE $ DEFINE LAVCS SYS1,SYS2,SYS3,SYS4/TABLE=SYSMAN$NODE_TABLE $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/NODE=(LAVCS) %SYSMAN-I-ENV, Current command environment: Individual nodes: SYS1,SYS2,SYS3,SYS4 Username ALEXIS will be used on nonlocal nodes |
The commands in this example set up the logical name table SYSMAN$NODE_TABLE, define a logical name (LAVCS), and use the logical name to define the command environment.
Temporarily modifies a user's current privileges and default device and directory.
SET PROFILE
None.
/DEFAULT=device:[directory]
Specifies the default disk device and directory name that the system should use in this environment to locate and catalog files./PRIVILEGES=(priv1,priv2...)
Specifies the privileges to add to the current privileges. Any enhanced privileges must be authorized./VERIFY
/NOVERIFY (default)
Specifies whether you want DCL verification (both procedure and image) for future DO commands.
The SET PROFILE command modifies process attributes for the current management environment. After considering the privilege requirements of commands that you intend to use in an environment, you can add or delete current privileges, if they are authorized. You can also set a new default device and directory, as well as use the SET PROFILE/[NO]VERIFY command to control DCL command verification in SYSMAN. Other attributes of your process remain constant. The profile is in effect until you change it, reset the environment, or exit from SYSMAN. The HP OpenVMS System Manager's Manual discusses profile changes in more detail.
#1 |
---|
SYSMAN> SET PROFILE/DEFAULT=WORK1:[ALEXIS] |
This command changes the default device and directory in the user account to directory ALEXIS on device WORK1.
#2 |
---|
SYSMAN> SET PROFILE/PRIVILEGES=(SYSPRV,CMKRNL)/VERIFY |
This command makes the authorized privileges, SYSPRV and CMKRNL, part of the current privileges, and turns on DCL verification. The privileges remain in effect until the environment changes, you enter another SET PROFILE command, or you exit.
Establishes the amount of time SYSMAN waits for a node to respond. Once the time limit expires, SYSMAN proceeds to execute the command on the next node in the environment.
SET TIMEOUT time
time
Specifies a delta time value, which has the following format:
hh:mm:ss[.cc.]
This is the amount of time that SYSMAN waits for a node to respond. SYSMAN waits indefinitely---by default it has no timeout period. Refer to the OpenVMS User's Manual for a description of delta time values.
None.
SYSMAN> SET TIMEOUT 00:00:30 %SYSMAN-I-TIMEVAL, timeout value is 00:00:30 SYSMAN> CONFIGURATION SHOW TIME System time on node NODE21: 19-JUN-2002 14:22:33 %SYSMAN-I-NODERR, error returned from node NODE22 %SMI-E-TIMEOUT, remote operation has timed out System time on node NODE23: 19-JUN-2002 14:23:15 |
This command establishes a timeout period of 30 seconds. Because NODE22 did not respond within 30 seconds, SYSMAN displays an error message and proceeds to execute the command on the next node in the environment.
Displays the target nodes or cluster where SYSMAN is executing commands.
SHOW ENVIRONMENT
None.
None.
The SHOW ENVIRONMENT command displays the current management environment. It can be the local cluster, local or remote nodes, or a nonlocal cluster. SYSMAN indicates if the environment is limited to individual nodes or if it is clusterwide. It also shows the current user name.The environment exists until you exit from SYSMAN or enter another SET ENVIRONMENT command.
#1 |
---|
SYSMAN> SHOW ENVIRONMENT %SYSMAN-I-ENV, Current command environment: Clusterwide on local cluster Username ALEXIS will be used on nonlocal nodes |
This command shows the current environment is the local cluster. User name ALEXIS will be used on other nodes in the cluster.
#2 |
---|
SYSMAN> SHOW ENVIRONMENT %SYSMAN-I-ENV, Current command environment: Clusterwide on remote cluster NODE21 Username ALEXIS will be used on nonlocal nodes |
This command shows that the command environment is a nonlocal cluster where NODE21 is a member.
#3 |
---|
SYSMAN> SHOW ENVIRONMENT %SYSMAN-I-ENV, Current command environment: Individual nodes: NODE22,NODE23 At least one node is not in local cluster Username ALEXIS will be used on nonlocal nodes |
This command shows that the command environment consists of two nodes.
Displays key definitions created with the DEFINE/KEY command.
SHOW KEY [key-name]
key-name
Specifies the name of the key whose definition you want displayed. See the DEFINE/KEY command for a list of valid key names.
/ALL
Displays all the key definitions in the specified state or states. Specifying a key name is not necessary./BRIEF
Displays only the key definition. By default, the system displays all the qualifiers associated with the key definition, including any specified state, unless you use the /BRIEF qualifier./DIRECTORY
Displays the names of all the states for which you have defined keys. If you have not defined keys, the SHOW KEY/DIRECTORY command displays the DEFAULT and GOLD states (which is the default SYSMAN keypad)./STATE=(state, state...)
Specifies the name of a state for which the specified key definitions are to be displayed. If you select more than one state name, separate them with commas and enclose the list in parentheses.
Specifies the name of the key whose definition you want displayed. See the DEFINE/KEY command for a list of valid key names.
SYSMAN> SHOW KEY/ALL DEFAULT keypad definitions: KP0 = "SHOW ENVIRONMENT" (echo) KP1 = "SHOW PROFILE" (echo) SYSMAN> |
This command displays all the key definitions currently in effect.
Displays the privileges and the default device and directory being used in the current environment.
SHOW PROFILE
None.
/DEFAULT
Displays the default disk device and directory name that the system uses in this environment to locate and catalog files./PRIVILEGES
Displays only the privileges in effect for the current environment.
The SHOW PROFILE command displays the privileges and the default device and directory that is being used in the current environment. You can modify these attributes with the SET PROFILE command.These values remain in effect until you change environments or enter another SET PROFILE command.
SYSMAN> SHOW PROFILE %SYSMAN-I-DEFDIR, Default directory on node NODE21 -- WORK1:[BERGERON] %SYSMAN-I-DEFPRIV, Process privileges on node NODE21 -- TMPMGX OPER NETMBX SYSPRV |
This command shows the default device and directory as well as current privileges.
Displays the amount of time SYSMAN waits for a node to respond. By default, there is no timeout period.
SHOW TIMEOUT
None.
None.
SYSMAN> SHOW TIMEOUT %SYSMAN-I-TIMEVAL, timeout value is 00:00:04.00 |
This command displays the current timeout value, which is 4 seconds.
Shuts down one or more nodes in an OpenVMS Cluster.The SHUTDOWN NODE command invokes SYS$SYSTEM:SHUTDOWN to shut down one node or multiple nodes, as you specify, in the current management environment. You can enter the shutdown command in one command line, instead of executing the SHUTDOWN.COM procedure on each node individually.
Requires SETPRV privilege or all of the following privileges: CMKRNL, EXQUOTA, LOG_IO, OPER, SYSNAM, SYSPRV, TMPMBX, WORLD.
SHUTDOWN NODE
None.
/AUTOMATIC_REBOOT
/NOAUTOMATIC_REBOOT (default)
Reboots the system automatically when the shutdown is complete./CLUSTER_SHUTDOWN
/NOCLUSTER_SHUTDOWN (default)
Shuts down the entire cluster.When you use the /CLUSTER_SHUTDOWN qualifier, each node suspends activity just short of shutting down completely, until all other nodes in the cluster have reached the same point in the shutdown procedure.
You must specify this option on every cluster node. If any one node is not shut down completely, the clusterwide shutdown cannot occur.
You should use the SET ENVIRONMENT/CLUSTER command before you issue a SHUTDOWN NODE/CLUSTER_SHUTDOWN command to ensure that all nodes in the cluster are shutting down.
/DISABLE_AUTOSTART
Specifies the number of minutes before shutdown when autostart queues running on the node are marked stop pending and are subject to failover to another node.Using this qualifier gives you control over when the autostart failover process begins. By default, the value equals that of the /MINUTES_TO_SHUTDOWN qualifier.
Determine the appropriate number of minutes for your configuration by weighing a smoother transition against completing a maximum number of jobs before shutdown. The larger the value, the smoother the transition will be. The smaller the value, the more jobs will execute on the node.
/INVOKE_SYSHUTDOWN (default)
/NOINVOKE_SYSHUTDOWN
Invokes a site-specific shutdown procedure./MINUTES_TO_SHUTDOWN=number
The number of minutes until shutdown occurs. If the system logical name SHUTDOWN$MINIMUM_MINUTES is defined, its integer value is the minimum value that you can enter. Therefore, if the logical name is defined as 10, you must specify at least 10 minutes to final shutdown or an error message displays. If the logical name is not defined, and you do not enter a value, 0 minutes is the default./POWER_OFF
Specifies that the system is to power off after shutdown is complete./REASON=text
The reason for the shutdown (one line)./REBOOT_CHECK
/NOREBOOT_CHECK (default)
Checks for basic operating system files and notifies you if any are missing. Be sure to replace missing files before rebooting./REBOOT_TIME=time
The time when you expect to reboot the system such as IMMEDIATELY, IN 10 MINUTES, 2 P.M., or 14:00:00. Shutdown displays this time in a shutdown message to users./REMOVE_NODE
/NOREMOVE_NODE (default)
Removes a node from the active cluster quorum. Use this qualifier when you do not expect the shut-down node to rejoin the cluster for an extended period.When you use the /REMOVE_NODE qualifier, active quorum in the remainder of the cluster is adjusted downward to reflect the fact that the removed node's votes no longer contribute to the quorum value. The shutdown procedure readjusts the quorum by issuing the SET CLUSTER/EXPECTED_VOTES command.
You can reset options by using the following command:
SYSMAN> STARTUP SET OPTIONS/NOVERIFY/NOCHECKPOINTINGFor more information about cluster management, see HP OpenVMS Cluster Systems.
/SAVE_FEEDBACK
/NOSAVE_FEEDBACK (default)
Records feedback data collected from the system since it was last booted and creates a new version of the AUTOGEN feedback data file, which you can use the next time you run AUTOGEN./SPIN_DOWN_DISKS
/NOSPIN_DOWN_DISKS (default)
Spins down disks. You cannot spin down the system disk.
Because SYSMAN enables you to define the target environment, you can perform a shutdown on your local node, your own cluster, or a subset of nodes on your cluster. If you are shutting down a local node, SYSMAN does not require you to remain logged in to the system during the shutdown, as long as you set the environment to the local node. See the SHUTDOWN NODE command examples and the SET ENVIRONMENT command for more information.In shutting down the system, the shutdown procedure:
- At decreasing time intervals, broadcasts a message to users to log out.
- Defines the system logical SHUTDOWN$TIME to reflect the value entered with the /MINUTES_TO_SHUTDOWN qualifier. For example, if you entered /MINUTES_TO_SHUTDOWN=10 at 12:00, the shutdown time would be 12:10.
To see if a shutdown is in progress or determine the actual time for shutdown, use the command SHOW LOGICAL SHUTDOWN$TIME.- At six minutes or less before shutdown, disables all nonoperator logins. If DECnet is running, it is shut down.
- At one minute before shutdown, stops batch and device queues and the system job queue manager.
- At zero minutes before shutdown, invokes the site-specific command procedure SYS$MANAGER:SHUTDWN.COM.
- Stops all user processes; however, system processes continue. Ancillary control processes (ACPs) may delete themselves when their mounted volumes are finally dismounted.
- Stops the secondary processor on dual-processor systems.
- Removes all installed images.
- Dismounts volumes and spins down disks, if you requested it. Does not spin down the system disk and the quorum disk, if a quorum disk is present.
- Closes the operator's log file.
- Invokes SYS$SYSTEM:OPCRASH to shut down the system.
- Displays the following message if you did not request an automatic reboot:
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM
If you requested an automatic reboot, the system reboots, provided the necessary controls are set.
#1 |
---|
SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> SHUTDOWN NODE/MINUTES_TO_SHUTDOWN=15/REBOOT_TIME="later"- _SYSMAN> /REASON="SOFTWARE UPGRADE"/REBOOT_CHECK/CLUSTER_SHUTDOWN |
The first command in this example ensures that all nodes in the cluster will shut down. The second command requests a shutdown for the entire cluster and a reboot check for any missing operating system files. The following messages are displayed to users on the cluster:
SHUTDOWN message on NODE21, from user SYSTEM at NODE21$0PA0: 12:00:00:20 NODE21 will shut down in 15 minutes; back up later. Please log off NODE21. SOFTWARE UPGRADE SHUTDOWN message on NODE22, from user SYSTEM at NODE22$0PA0: 12:00:00:22 NODE22 will shut down in 15 minutes; back up later. Please log off NODE22. SOFTWARE UPGRADE SHUTDOWN message on NODE23, from user SYSTEM at NODE23$0PA0: 12:00:00:24 NODE23 will shut down in 15 minutes; back up later. Please log off NODE23. SOFTWARE UPGRADE
#2 |
---|
SYSMAN> SET ENVIRONMENT/NODE=0 Password: SYSMAN> SHUTDOWN NODE/MINUTES=120 %SYSMAN-I-SHUTDOWN, SHUTDOWN request sent to node SYSMAN> EXIT $ LOGOUT |
Previous Next Contents Index