NET/MASTER Management Services (MS) System Management Guide

Using UMS to Support Operations on a Network
Managing User Access and Privileges
115414 NonStop NET/MASTER MS System Management Guide 4–25
When a virtual user processes commands and NCL procedures, NonStop
NET/MASTER MS enforces the security restrictions established for the user who
submitted the commands to the virtual user. Therefore, the submitter’s command
authority level and GUID (for external utilities) are enforced on commands executed
by the virtual user.
If you want the virtual user to communicate with a remote NonStop NET/MASTER
MS system, you must add a user ID definition record for the virtual user to the UMS
database of the local system and of the remote system. You must also grant the user
ID privileges for logging on to and from a remote system, as appropriate.
Using UMS to Support
Operations on a
Network
Users who log on to remote NonStop NET/MASTER MS and SOLVE management
services systems must have a user ID defined to both management applications.
Additionally, the user ID definition record on each system must be properly
configured for access to and from a remote management application.
Enabling a user ID to log on to a remote management application allows use of these
remote operations commands:
SIGNON link-name command, used to log on to a remote NonStop NET/MASTER
MS system
ROUTE command, used to send a command to a remote NonStop NET/MASTER
MS system
Consider the example of the network in Figure 9-5 in Section 9, “Supporting Remote
Operations.” Suppose users at the central control node, \NODEA, require access to
each of the satellite nodes. You must define each user to both the NonStop
NET/MASTER MS system on \NODEA and the system on each satellite node that the
user will access. At a minimum, you must perform these tasks:
1. Using UMS on \NODEA, enter Y in the Logon to Remote System field of the
user’s user ID definition record.
2. Using UMS on each satellite node that the user will access, add a user ID definition
record for the user, if one does not exist. Be sure to enter Y in the Logon From
Remote System field of the user’s user ID definition record.
Note To issue the ROUTE command, a user ID must have the same password on the local and remote
NonStop NET/MASTER MS systems. If the passwords differ, the user can use the ROUTE command
after using the SIGNON PASSWORD command to specify the password on the remote NonStop
NET/MASTER MS system. Alternatively, the user can log on to the remote system and attempt to change
the password to match that on the local system.
When performing remote operations with the Distributed Systems Network
Management (DSNM) command set, the GUID and remote password requirements
vary according to the way in which a user issues DSNM commands.