NET/MASTER Management Services (MS) System Management Guide

Restricting Access to Commands
Customizing the Operations Environment
5–10 115414 NonStop NET/MASTER MS System Management Guide
For example, you could change the title to one that indicates the name of a particular
system by issuing a command like this:
TITLE DEVELOPMENT SYSTEM-B OPERATOR CONTROL SERVICES
The OCS window would appear similar to the one shown next.
(07:42) ----------- DEVELOPMENT SYSTEM-B OPERATOR CONTROL SERVICES -----------
TITLE DEVELOPMENT SYSTEM-B OPERATOR CONTROL SERVICES
NNM0363 NEW TITLE SET
_____________________________________________________________________________
---------- ------------------ NonStop NET/MASTER D30 ---------------- --------
M=> TITLE DEVELOPMENT SYSTEM-B OPERATOR CONTROL SERVICES
To change the title during the startup phase, include the TITLE command in the INIT
or READY NCL procedure.
Restricting Access to
Commands
There are several ways to restrict access to NonStop NET/MASTER MS commands.
First, you can replace the command with an NCL procedure, as described in
“Customizing NonStop NET/MASTER MS Commands,” later in this section. The
NCL procedure can test for conditions and either grant or deny use of the command,
based on the results of the test. You can also change the minimum command
authority level required to invoke either a NonStop NET/MASTER MS command or a
command of a Guardian utility, such as FUP, PUP, or COUP.
Changing Command
Authority Levels for
NonStop NET/MASTER MS
Commands
You can also restrict access to a command and its operands by changing the minimum
command authority level required to use the command or operand. Each NonStop
NET/MASTER MS command is assigned an authority level from 0 through 255. To
execute the command, a user must have a command authority level that is equal to or
greater than that of the command.
Use the SYSPARMS CMDAUTH command to change the minimum authority level
required to invoke a NonStop NET/MASTER MS command or any command
operand.