HP OpenVMS Systems Documentation
OpenVMS System Manager's Manual
2.3.2 Enabling a Remote System to Execute SYSMAN Commands
Any node that is part of an OpenVMS Cluster system normally starts the SMISERVER process in the system startup procedure SYS$SYSTEM:STARTUP.COM. (The system parameter VAXCLUSTER on the node must have a value of 1 or more.)
For more information about SYSTARTUP_VMS.COM, see Section 5.2.7.
You can also enter this command interactively to restart the SMISERVER
process without rebooting the system.
When you use SYSMAN, you must define the management environment you will be working in. The management environment is the node or nodes on which subsequent commands will execute.
By default, the management environment is the local node (the node from which you execute SYSMAN). To execute commands on one or more other nodes, you can redefine the management environment to be any of the following:
Refer to Figure 2-2 during the following discussion of management environments.
Figure 2-2 Sample SYSMAN Management Environment
You can use NODE21 as the management environment, or you can define the environment to be any node, group of nodes, or cluster shown in Figure 2-2.
If you execute SYSMAN from NODE21, then NODE21 is the local node; it is
the management environment when SYSMAN starts. All other nodes are
To define the management environment, use the SYSMAN command SET ENVIRONMENT. Whenever you redefine an environment, SYSMAN displays the new context. You can always verify the current environment with the SHOW ENVIRONMENT command.
When you are not working on your local node or within your own cluster, your environment is a nonlocal environment. SYSMAN makes this distinction for security reasons; when you are defining a nonlocal environment, such as a different cluster, SYSMAN prompts for a password. SYSMAN also prompts for a password when you attempt to manage a system under a different user name. You can change your user name by using the /USERNAME qualifier with SET ENVIRONMENT.
A SYSMAN environment remains in effect until you change it or exit from
You can define a management environment to be any node available through DECnet. To define one or more nodes to be your management environment, use the SET ENVIRONMENT/NODE command.
For the following examples, refer to Figure 2-2; assume you are logged in to NODE 21.
184.108.40.206 Using Logical Names to Organize Management Environments
If you want to organize the nodes in your cluster according to specific categories (for example, all CI-based nodes or all nodes with C installed), you can define logical names to use with the SET ENVIRONMENT/NODE command, as follows:
You can also define logical names for VAX and Alpha nodes in a dual-architecture OpenVMS Cluster system, as explained in Section 22.6.
The following example demonstrates how you can define multiple logical names to organize several management environments:
220.127.116.11 Defining an OpenVMS Cluster Environment
To define your management environment to be an OpenVMS Cluster system, use the SET ENVIRONMENT/CLUSTER command.
In SYSMAN, OpenVMS Cluster environments can be one of two types:
To expand the management environment in Figure 2-2 from NODE21 to Cluster 1, enter the following command from NODE21:
In the OpenVMS Cluster environment shown in Figure 2-2, SYSMAN executes commands on all nodes in Cluster 1, namely NODE21, NODE22, and NODE23.
If you use the /CLUSTER and /NODE qualifiers together, the environment becomes the OpenVMS Cluster system where the given node is a member. For example, to perform management tasks on Cluster 2 in Figure 2-2, enter SET ENVIRONMENT with the /CLUSTER qualifier and name one node within Cluster 2 using the /NODE qualifier:
When you use SYSMAN across OpenVMS Cluster systems, SYSMAN establishes a profile that contains your rights, privileges, and defaults, and verifies that you are an authorized user. If you encounter privilege problems when using SYSMAN, it helps to know how SYSMAN determines your profile.
SYSMAN looks for three possible scenarios when determining your profile:
The profile does not include symbolic names, logical names, preset
terminal characteristics, or key definitions established through a
login command procedure. The only environment that has the attributes
defined in a login command procedure is the local node from which you
are executing SYSMAN.
This profile is in effect until you change it with SET PROFILE, reset the environment (which may change your profile automatically), or exit from SYSMAN.
The SET PROFILE command temporarily changes the attributes of your
current local process. However, when you exit from SYSMAN, all
attributes are restored to the values that were current when SYSMAN was
Frequently, system management commands require special privileges. You might need to add privileges before you execute certain commands in an environment. System managers usually have the same privileges on all nodes; if you do not have the required privileges on a node, SYSMAN cannot execute the command and returns an error message.
The following example makes SYSPRV one of your current privileges:
18.104.22.168 Changing Your Default Device and Directory
Use the SET PROFILE/DEFAULT command to reset the default device and directory specification for your process and all server processes in the environment.
Most often, the default device and directory specified in your UAF record is a first-level directory in which you create and maintain files and subdirectories. SYSMAN uses this default device and directory name when resolving file specifications. It also assigns the default device and directory name to any files that you create during a session.
In some cases, you might need to change the default device and directory in your SYSMAN profile. For example, you might have a directory containing command procedures as well as some system management utilities that require the default directory to be SYS$SYSTEM.
The following example sets the default device and directory to DMA1:[SMITH.COM]:
2.3.7 Setting DCL Verification
Use the SET PROFILE/VERIFY command to turn on DCL verification, which displays DCL command lines and data lines as they execute.
SYSMAN can execute DCL commands using the DO command. By default, SYSMAN DCL verification is turned off.
2.3.8 Executing DCL Commands from SYSMAN
The SYSMAN command DO executes DCL command procedures and SYSMAN command procedures on all nodes in an OpenVMS Cluster environment. In an OpenVMS Cluster environment or in any environment with multiple nodes, you enter a set of commands once, and SYSMAN executes the commands sequentially on every node in the environment. SYSMAN displays the name of each node as it executes commands, or an error message if the command fails.
If a node does not respond within a given timeout period, SYSMAN displays a message before proceeding to the next node in the environment. You can specify a timeout period with the SET TIMEOUT command.
Each DO command executes as an independent subprocess, so no process context is retained between DO commands. For this reason, you must express all DCL commands in a single command string, and you cannot run a procedure that requires input.
In an OpenVMS Cluster environment, SYSMAN executes DO commands sequentially on all nodes in the cluster. After a command completes or times out on one node, SYSMAN sends it to the next node in the environment. Any node that is unable to execute a command returns an error message.
For more information about using the DO command to manage an OpenVMS Cluster system, see Section 22.6. You can also refer to the OpenVMS System Management Utilities Reference Manual for a complete description of the SYSMAN command DO.
In the following example, SYSMAN runs the INSTALL utility and makes a file known on all nodes in the cluster when you enter the commands from the local node:
2.3.9 Creating SYSMAN Command Procedures
The SYSMAN execute procedure (@) command executes SYSMAN command procedures on each node in the environment.
The following example creates and executes a SYSMAN command procedure to display the current date and system time for each OpenVMS Cluster node:
2.3.10 Setting Up SYSMAN with an Initialization File
You can create an initialization file that is used each time you invoke SYSMAN. In the initialization file, you can perform tasks such as defining keys and setting up your environment.
The default file specification for the SYSMAN initialization file is SYS$LOGIN:SYSMANINI.INI. If you want your SYSMAN initialization file to have a different file specification, you must define the logical name SYSMANINI to point to the location of the file. The following is a sample initialization file that defines several keys:
2.4 Using OPCOM to Communicate with System Users
The operator communication manager (OPCOM) is a tool for communicating with users and operators on the system. OPCOM allows you to perform the following functions:
1These functions are used in sites where operators are assigned to help users mount disk or tape volumes and printer forms.
2.4.1 Understanding OPCOM
Figure 2-3 illustrates the function of OPCOM.
Figure 2-3 Operator Communication Manager (OPCOM)