MCR SYSMAN SET — VMS 5.4-3
Additional information available:
ENVIRONMENT
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
Additional information available:
Qualifiers
Additional information available:
/CLUSTER
Directs SYSMAN to apply subsequent commands 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
/NODE=(node1,node2,...)
Specifies that SYSMAN execute subsequent commands on the given
nodes. If accompanied by the /CLUSTER qualifier, the environment
becomes the cluster where the given 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.
/USERNAME
/USERNAME=username
Specifies that this user name should be used for access control
purposes on another node. SYSMAN uses the current user name if
none is supplied. The utility prompts for a password whenever a
new user name is specified.
Examples
1. SYSMAN> SET ENVIRONMENT/CLUSTER
%SYSMAN-I-ENV, Current command environment:
Clusterwide on local cluster
Username ALEXIS will be used on nonlocal nodes
The commands in this example define the command environment as
the local cluster. SYSMAN confirms the new environment.
2. SYSMAN> SET ENVIRONMENT/NODE=CLACK/CLUSTER
Remote Password:
%SYSMAN-I-ENV, Current command environment:
Clusterwide on remote node CLACK
Username ALEXIS will be used on nonlocal nodes
The command in this example establishes a management
environment on the cluster where node CLACK is a member. SYSMAN
prompts for a password because it is a nonlocal environment.
3. SYSMAN> SET ENVIRONMENT/NODE=(LESETH,JOSHUA,TORIN)
%SYSMAN-I-ENV, Current command environment:
Individual nodes: LESETH,JOSHUA,TORIN
Username ALEXIS will be used on nonlocal nodes
The command in this example 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.
PROFILE
Temporarily modifies a user's current privileges and default
device and directory.
Format
SET PROFILE
Additional information available:
Qualifiers
Additional information available:
/DEFAULT
/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
/PRIVILEGES=(priv1,priv2...)
Specifies the privileges to add to the current privileges. Any
enhanced privileges must be authorized.
/VERIFY
/VERIFY
/NOVERIFY (default)
Allows you to specify whether you want DCL verification (both
procedure and image) for future DO commands.
Examples
1. SYSMAN> SET PROFILE/DEFAULT=WORK1:[ALEXIS]
The command in this example changes the default device and
directory in the user account to directory ALEXIS on device
WORK1.
2. SYSMAN> SET PROFILE/PRIVILEGES=(SYSPRV,CMKRNL)/VERIFY
The command in this example 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.
TIMEOUT
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.
Format
SET TIMEOUT time
Additional information available:
Parameter
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. By default, there is no timeout period, so SYSMAN waits indefinitely. See the VMS DCL Concepts Manual for a description of delta time values.
Example
SYSMAN> SET TIMEOUT 00:00:30
%SYSMAN-I-TIMEVAL, timeout value is 00:00:30
SYSMAN> CONFIGURATION SHOW TIME
System time on node ASCONA: 19-APR-1990 14:22:33
%SYSMAN-I-NODERR, error returned from node LUGANO
%SMI-E-TIMEOUT, remote operation has timed out
System time on node JOSHUA: 19-APR-1990 14:23:15
The command in this example establishes a timeout period of 30
seconds. Because node LUGANO did not respond within 30 seconds,
SYSMAN displays an error message and proceeds to execute the
command on the next node in the environment.