NET/MASTER Management Services (MS) System Management Guide

Phase 2: Start NonStop NET/MASTER MS

Starting NonStop NET/MASTER MS

115414 NonStop NET/MASTER MS System Management Guide 2–7

Phase 2: Start

NonStop NET/MASTER

To start a NonStop NET/MASTER MS system using the default startup configuration,

follow these steps:

1. Determine which Guardian user ID will own the NonStop NET/MASTER MS and

DSNM processes and files.

The Guardian user ID used to start NonStop NET/MASTER MS, called the

“NonStop NET/MASTER MS system user ID,” owns all processes started by the

NonStop NET/MASTER MS system, including DSNM processes.

Additionally, all DSNM commands entered by users are executed under the

NonStop NET/MASTER MS system user ID. Accordingly, if you use DSNM

commands to manage subsystem objects, select a Guardian user ID that can issue

commands to the appropriate subsystem manager processes.

Note The NonStop NET/MASTER MS system user ID does not own the DSNM processes of an externally

started or shared DSNM environment. Therefore, the Guardian user ID you select to start NonStop

NET/MASTER MS is not significant when issuing DSNM commands to an externally started or shared

DSNM environment. See Section 11, “Configuring the Processing Environment,” for more information

about configuring the DSNM environment.

The NonStop NET/MASTER MS system user ID also owns any files created by

NonStop NET/MASTER MS. Such files include, but are not limited to, databases

used for security administration and message logging.

2. Log on to your node with the Guardian user ID you selected in Step 1.

3. If the NonStop NET/MASTER MS system user ID has a default security string

other than NOOO, you may want to change the default security string to NOOO.

The Guardian User’s Guide explains the procedure for setting a default security

string.

All files created by NonStop NET/MASTER MS have the security string of the

NonStop NET/MASTER MS system user ID. Tandem recommends a security

string of NOOO, but this is optional.

4. If you want to control communications subsystems, verify that the appropriate

manager processes are executing:

To manage Expand objects, verify that $ZEXP is executing.

To manage AM3270, TR3271, or X25AM objects, verify that $ZNET is

executing.

To manage SNAX/XF or SNAX/CDF objects, verify that $SSCP is executing.