Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

Process Parameters
5-2
109759—Distributed Systems Network Management (DSNM) Subsystem Interface
Development Guide
DSNM Process Startup Functions
Process Parameters
The standard DSNM process parameters accepted from the startup message are
discussed next. (TESTMODE, CONFIG, STARTUP, and DEBUG are used for
development testing only.)
DSNM env-name
specifies the $SYSTEM.SYSTEM.DSNM section name to be used by this process.
The process uses the environment defined in ?SECTION env-name in
$SYSTEM.SYSTEM.DSNM. If both the DSNM and CONFIG parameters are
omitted, the unnamed section (blank) of $SYSTEM.SYSTEM.DSNM is used.
If $SYSTEM.SYSTEM.DSNM exists, it must contain a section named env-name
or a fatal error is reported.
COMPONENT component-name
specifies the process component name. This value is used for retrieval of parameter
values from the DSNMCONF file.
For I processes, COMPONENT is usually the name of the subsystem the I process
handles. For I processes that handle more than one subsystem (such as the SCP
I process), the component name is an arbitrary name chosen by the developer of the
process (for example, COMM is the component name for the SCP I process).
MYSYSTEM system-name
specifies the acting home system, if the process can act as if a remote system were
its home system.
TESTMODE num
any nonzero value specifies that the process is running in test mode; 0, the default,
specifies production mode. This parameter is valid only if the process is compiled
in test mode; you receive a fatal error if the process is compiled in production mode.
Test mode forces the STARTUP [PARAMS] value in $SYSTEM.SYSTEM.DSNM
to default to YES, and enables processing of the CONFIG, STARTUP, and DEBUG
process parameters.
CONFIG filename [filename] ...
specifies a DSNMCONF search list of up to three configuration files, which
overrides the DSNMCONF file pointed to in $SYSTEM.SYSTEM.DSNM.
CONFIG allows you to specify multiple configuration files for testing purposes
only. This allows you to maintain your subsystem, CI, and I process configuration
records separate from your installation’s site-specific production environment
configuration. CONFIG values are ignored if TESTMODE is not enabled.
Note. To compile in test mode, set toggle 1 during compilation (SETTOG 1). Recompile
all programs without SETTOG 1 before placing them in production.