NET/MASTER Management Services (MS) System Management Guide

Phase 1: Perform Initial Installation Tasks
Starting NonStop NET/MASTER MS
2–6 115414 NonStop NET/MASTER MS System Management Guide
Task 4: Secure Files In this task, you secure the files. Refer to the Safeguard Administrator’s Manual and the
Safeguard User’s Guide if you want to use Safeguard security features to refine file
security.
1. Secure all program files in the $isv-vol.ZNNM subvolume.
If you are going to use NonStop NET/MASTER MS only on the local system,
issue the following command against the program files:
FUP SECURE file-name , %7727
The command changes the security string to - - O -, which gives read, write,
and purge authority to the super ID (255,255), and execute authority to the
local owner of the NonStop NET/MASTER MS program files.
If you are going to start NonStop NET/MASTER MS from a remote node,
issue the following command against the program files:
FUP SECURE file-name , %7767
The command changes the security string to - - U -, which gives read, write,
and purge authority to the super ID (255,255), and execute authority to the
local or remote owner of the NonStop NET/MASTER MS program files.
Note Tandem recommends that you strictly control execute access to the NonStop NET/MASTER MS object
files. Any user who starts a NonStop NET/MASTER MS system can create a user ID definition record
and allow the user to use the super ID (255,255).
A warning message is generated if the file security of any licensed object file is not - - O - or - - U -.
2. Secure the NCL and panel description source and object files so that they can be
read by the Guardian user ID that owns the NonStop NET/MASTER MS
processes.
$isv-vol.ZNNMNDO contains the NCL object file, named NCODE.
$isv-vol.ZNNMNDS contains the NCL source files.
$isv-vol.ZNNMPDS contains the panel description object file, named PCODE,
and the panel description source files.
Note that NCL and panel description files do not require execute access because
NCL procedures are not executed in the Guardian environment.
3. If you use DSNM to manage subsystem objects, refer to the Distributed Systems
Management Solutions (DSMS) System Management Guide to determine the security
requirements of the DSNM processes controlled by NonStop NET/MASTER MS.