NET/MASTER Management Services (MS) System Management Guide

Using UMS to Manage User Privileges
Managing User Access and Privileges
115414 NonStop NET/MASTER MS System Management Guide 4–31
Table 4-7. Command Authority Levels
Authority
Level Application
0 Commands that change nothing, with the possible exception of the current user’s
operations environment. Commonly used with informational inquiries.
1 Commands used for controlling system and network resources. Associated with
commands that affect the most modest changes outside the current user’s environment.
2 Commands that can significantly affect other users.
3 Commands that can activate important changes in the computing environment, such as
altering the states of objects.
4 Commands that can change the configuration of NonStop NET/MASTER MS and other
subsystems.
255 Commands that enable users to circumvent NonStop NET/MASTER MS security;
examples include the TACL RUN command and the unrestricted PROGRUN command.
You can change the minimum command authority level required to use commands:
The minimum command authority level required to use NonStop NET/MASTER
MS commands and their operands can be changed by using the SYSPARMS
CMDAUTH command. See Section 5, “Customizing the Operations
Environment,” for additional information.
The minimum command authority level required to use external utilities and
members of their command sets can be changed by using Utility Maintenance
Services. See Section 6, “Managing Access to External Utilities and Applications,”
for details.
NCL Library Subvol Field You can create a user procedure library for the user ID by entering the name of a
volume and subvolume in the NCL Library Subvol field of the UMS : User Attributes
panel. A user library contains NCL procedures that are created and used by the user.
A user with a user library is taken to that library subvolume upon entering Edit
Services. The user procedure library is searched first when a user invokes an NCL
procedure. Section 3, “Configuring NonStop NET/MASTER MS,” discusses the
complete search path.
NCL Object File Name Field You can specify the name of a file that contains the object code of NCL procedures
invoked by the user in the NCL Object File Name field. This enables the user to store
code in a file other than the customized and distributed object files specified by the
PARAM NCLCUSTOBJ and PARAM NCLDISTOBJ commands, respectively. Unless
otherwise specified, the user object file resides in the user object file library
subvolume, which is specified by the PARAM NCLOBJLIB operand.