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–69
To use these processes, follow the instructions provided in “Configuring DSNM
Processes,” earlier in this subsection, for defining the processes you want to use. Note
that if you configure any DSNM processes in the CONFIG file, the file must contain a
definition for each DSNM process that you want to start. Therefore, if you add the
event monitoring capability by defining DBI, OMON, and some event monitoring
processes, the CONFIG file must also contain definitions for the subsystem interface
processes and the command server.
The Distributed Systems Management Solutions (DSMS) System Management Guide
contains a detailed explanation of each process.
Distributing DSNM Virtual
Memory Activity
The Distributed Systems Management Solutions (DSMS) System Management Guide
describes the default volumes and subvolumes that DSNM processes use for virtual
memory activity. Refer to that manual for an explanation of the procedures used to
configure DSNM virtual memory activity.
Configuring NonStop
NET/MASTER MS to Share
DSNM
A NonStop NET/MASTER MS system can use an external DSNM environment, that
is, one that belongs to either a stand-alone DSMS system or the Integrated Operations
Console (IOC). The practice of using a DSNM environment that another management
application controls is known as sharing a DSNM environment.
You can configure a NonStop NET/MASTER MS system to share a DSNM
environment with other management applications by using PARAM command
operands to identify the names of the command server processes in the remote DSNM
environment. To use a remote DSNM environment, include the following PARAM
command operands in the CONFIG file: CMDSVR and DSNMSECTION.
Use the CMDSVR operand to specify the name of an externally-started command
server process for the remote DSNM system. Specify CMDSVR as a valid process
name. For example, to specify a command server named $BDCM, include the
following command in the CONFIG file:
PARAM CMDSVR=$BDCM
You can specify up to 10 command server processes. If you cannot define all
command server process names in one line, repeat the PARAM CMDSVR
command to specify additional names. If you define an externally-started
command server, NonStop NET/MASTER MS does not automatically configure
any DSNM processes.
Use the DSNMSECTION operand to specify the section of the
$SYSTEM.SYSTEM.DSNM file that names the externally-started DSNM
environment’s configuration file.
If you want to use the OPSYS command to start sessions with
conversational-mode Guardian utilities, the CONFIG file must include commands
for starting a CIP process. DSNM environments started by DSMS and the IOC do
not use the CIP process.