NET/MASTER Management Services (MS) System Management Guide

Using UMS to Support Operations on a Network
Managing User Access and Privileges
4–26 115414 NonStop NET/MASTER MS System Management Guide
In two cases, a user requires a GUID on the local node and on the remote node, as well
as remote Guardian passwords for the GUIDs on the two nodes:
When a user starts external utilities on the local node and applies external utility
commands to objects on remote nodes. For example, if a user on the local node
starts a session with the Subsystem Control Facility (SCF) and uses an SCF ALTER
command to change the characteristics of a communications line on a remote
node, the user must have a GUID on both the local and the remote node, as well as
remote passwords for the two GUIDs.
When a user applies DSNM commands from the local NonStop NET/MASTER
MS system to objects on a remote node. For example, if a user on the local node,
named \NODE1, applies the following command to a communications line on the
remote node, named \NODE2, the user requires a GUID on \NODE1 and
\NODE2, as well as remote passwords for the two GUIDs:
OPSYS START LINE \NODE2.$LINE1
A user does not require a GUID on a remote node or a remote password to use the
ROUTE link-name OPSYS command to send DSNM commands to a remote NonStop
NET/MASTER MS system.
Consider the example of two nodes, named \NODE1 and \NODE2, where \NODE2
has a communications line named $LINE1. On \NODE1, the INMC link to \NODE2
is named NODE2. A user who issues the following command does not require a
GUID on \NODE2; the DSNM command executes under the GUID that was used to
start the NonStop NET/MASTER MS system on \NODE2:
ROUTE NODE2 OPSYS START LINE $LINE1
For additional information about the use of DSNM commands, refer to the NonStop
NET/MASTER MS Operator’s Guide and to the User’s Guide to Distributed Systems
Network Management (DSNM) Commands.