Defines the nodes or cluster to which subsequent commands apply. Requires OPER or SETPRV privilege on all nodes in the target environment. Format SET ENVIRONMENT
1 – Qualifiers
1.1 /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.
1.2 /NODE
/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 VSI OpenVMS System Manager's Manual.
1.3 /USERNAME
/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.
2 – Description
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.
3 – Examples
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.