NET/MASTER Management Services (MS) System Management Guide

Using NonStop NET/MASTER MS With and Without DSNM
Configuring the Processing Environment
115414 NonStop NET/MASTER MS System Management Guide 11–71
To use the external DSNM environment, include these commands in the CONFIG file:
== Starting a CIP process because the shared DSNM environment
== does not include one
PARAM PROCESSOBJECT=$DATA.ZDSMS.CIP
PARAM PROCESSNAME=$ZD05
PARAM PROCESSPARAM="DSNM ZNNMCONF"
PARAM CIPPROCESS=CIP1
== Specifying the command server of the shared DSNM
== environment and the section of the $SYSTEM.SYSTEM.DSNM
== file that names the environment’s DSNM
= configuration file
PARAM CMDSVR=$ZDCM
PARAM DSNMSECTION=ZNNMCONF
If the CONFIG file includes both the PARAM CMDSVR and the PARAM
CMDPROCESS commands, NonStop NET/MASTER MS uses the command server
process specified by the PARAM CMDSVR command. Although the NCP starts the
command server specified by the PARAM CMDPROCESS command, the NonStop
NET/MASTER MS system supervised by the NCP uses only the command server
specified by the PARAM CMDSVR command. This is true regardless of the order in
which the PARAM CMDSVR and PARAM CMDPROCESS commands appear in the
CONFIG file.
Configuring NonStop
NET/MASTER MS to Not
Use DSNM
In rare circumstances, you may wish to start NonStop NET/MASTER MS without
starting DSNM. The effect is that you lose all the DSNM command capability
associated with the OPSYS command. NCL procedure development and limited
training exercises are examples of reasons for which you could use NonStop
NET/MASTER MS without DSNM.
To start NonStop NET/MASTER MS without DSNM, configure valid but nonexistent
process names for the command server process and the CIP in the CONFIG file. The
following example shows nonexistent process names:
PARAM CIP=$JUNK1
PARAM CMDSVR=$JUNK2