Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

Format of the DSNMCONF File
6-4
109759Distributed Systems Network Management (DSNM) Subsystem Interface
Development Guide
Configuring a New Subsystem Into DSNM
A CONFIG statement search list may specify nonexistent files; this is not an error.
A nonexistent file is treated as if it were present but empty. It is ignored, and the
search continues with the next configuration file. This is also true of the default
DSNM configuration file (objsubvol.DSNMCONF), if there is no CONFIG
statement for an environment.
The Tandem configuration file $SYSTEM.SYSTEM.ZDSNCONF is searched in
addition to the files listed in a CONFIG statement; it is always the last file on the
search list. $SYSTEM.SYSTEM.ZDSNCONF must be present.
STARTUP [ PARAMS ] { YES | NO }
determines whether DSNM configuration parameters from the startup message are
used:
If STARTUP is YES, DSNM configuration parameters in the process startup
message override or supplement the value of the corresponding parameter in the
DSNM configuration search list. YES is the default.
If STARTUP is NO, DSNM configuration parameters in the process startup
message are ignored.
Format of the DSNMCONF File
DSNMCONF files contain startup parameters for the various DSNM processes,
subsystem and subsystem object type configuration information, and subsystem CI
configuration information. A DSNMCONF file is a key-sequenced file with a
ZDSN^DDL^DSNMCONF^DEF record definition. Each record represents a single
instance of a parameter and contains the following fields:
Key Field Description
SYSTEM Identifies the Tandem node to which the parameter applies.
SUBSYS Identifies the product to which the parameter applies; for DSNM
components supplied by Tandem, the SUBSYS key field must be
“DSNM.
CLASS Identifies the class of DSNM entities to which the parameter
applies.
COMPONENT Identifies the member of the class to which the parameter applies;
the component name often identifies the subsystem that the
DSNM entity supports.
PARAMETER Identifies the parameter defined by the record.
SEQUENCE Distinguishes multiple instances of a parameter. For multivalued
parameters, the valid range is 1 to 9999; for single-valued
parameters, this field is blank.
VALUE Contains the value of the parameter. Valid values depend on the
particular parameter.