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–67
If you configure any of the DSNM processes, the CONFIG file must contain
instructions for starting the OMON, DBI, and event monitor processes, if required, in
addition to the DSNM processes you configure. If a CONFIG file includes any
configuration for a DSNM process started by NonStop NET/MASTER MS, the file
must contain process definitions for every DSNM process required by the processing
environment.
For example, if your system does not use X25AM and you do not want the DSNM
event monitoring and subsystem interface processes for the X25AM subsystem to start,
create a CONFIG file that defines a configuration for every DSNM process except the
two processes that you want to exclude.
Configuring a Conversational Interface Process
When defining a CIP process in the CONFIG file, use the CIPPROCESS operand to
specify the process type and the logical name of the process. For example, to configure
a CIP named $ZD05, include the following lines in the CONFIG file:
PARAM PROCESSOBJECT=$DATA.ZDSMS.CIP
PARAM PROCESSNAME=$ZD05
PARAM PROCESSPARAM="DSNM ZNNMCONF"
PARAM CIPPROCESS=CIP_01
You can define up to 10 CIP processes.
Configuring a Command Server Process
When defining a command server process in the CONFIG file, use the CMDPROCESS
operand to specify the process type and the logical name of the process. For example,
to configure a command server process named $ZDCM, include the following lines in
the CONFIG file:
PARAM PROCESSOBJECT=$DATA1.ZDSMS.CMDSVR
PARAM PROCESSNAME=$ZDCM
PARAM PROCESSPARAM="DSNM ZNNMCONF"
PARAM CMDPROCESS=CMDSVR
If the CONFIG file contains a process definition for a command server process, include
process definitions for the remaining DSNM processes that you want to start.