Technical data

Using OpenVMS System Management Utilities and Tools
2.3 Using SYSMAN to Centralize System Management
• If the environment is an OpenVMS Cluster systen and does not have common
SYSUAF and RIGHTSLIST databases, SYSMAN checks the SYSUAF on the
target nodes to see if you are an authorized user. If you are an authorized
user, SYSMAN copies your profile from the SYSUAF on the target nodes to
the SMISERVER process on the target nodes.
• If the environment has nodes that are not part of your local cluster, or if you
have recently changed your user name, SYSMAN prompts you for a password
before it checks the SYSUAF on the target node. If you enter the correct
password and the SYSUAF shows that you are an authorized user, SYSMAN
copies your profile from the SYSUAF on the target nodes to the SMISERVER
process on the target nodes.
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.
2.3.6 Adjusting Your SYSMAN Profile
Use the SYSMAN command SET PROFILE to change your SYSMAN
management profile. The qualifiers /PRIVILEGES, /DEFAULT, and /VERIFY
enable you to change the following attributes of the SMISERVER process:
Attribute Qualifier For More Information
Current privileges /PRIVILEGES Section 2.3.6.1
Default device and directory /DEFAULT Section 2.3.6.2
DCL verification of DO
commands
/VERIFY Section 2.3.7
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 invoked.
2.3.6.1 Changing Your Current Privileges
The SYSMAN command SET PROFILE/PRIVILEGES temporarily changes your
current privileges in an environment.
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.
Example
The following example makes SYSPRV one of your current privileges:
Using OpenVMS System Management Utilities and Tools 2–17