Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide
Configuring a New Subsystem Into DSNM
Distributed Systems Network Management (DSNM) Subsystem Interface Development 
Guide—109759 6-3
The $SYSTEM.SYSTEM.DSNM File
The format of $SYSTEM.SYSTEM.DSNM is as follows:
?SECTION env-name
names the DSNM environment. Each section in $SYSTEM.SYSTEM.DSNM 
defines a separate environment. 
The first section in $SYSTEM.SYSTEM.DSNM is always the unnamed section. 
The unnamed section defines the default environment. The ?SECTION statement is 
optional for the unnamed section. An unnamed (blank) ?SECTION statement that is 
not the first section in the file is ignored. If the file begins with a named ?SECTION 
statement, an unnamed section is considered to be present but empty. 
A ?SECTION statement is followed by zero or more lines of environment definition 
statements and comments. A section is terminated by the next ?SECTION statement 
or the end of the file. Blank lines are allowed. 
The environment definition statements are:
CONFIG [ FILE ] filename [ filename [ filename ] ]
STARTUP [ PARAMS ] { YES | NO }
Both statements are optional. If more than one CONFIG or STARTUP statement is 
present in the section, all but the first are ignored.
CONFIG [ FILE ] filename [ filename [ filename ] ]
defines a search list of up to three configuration files that the DSNM processes 
search in the order listed for configuration parameters. The default for CONFIG 
filename is objsubvol.DSNMCONF.
objsubvol is the subvolume on which the process program file resides.
A CONFIG statement with a blank search list is not valid.  You must omit the 
CONFIG statement altogether to default the search list to 
objsubvol.DSNMCONF.
If a CONFIG statement is present but one or more of the file names is not fully 
qualified, objsubvol qualifies the first file name (at the local node). The 
remaining file names are qualified by the node, volume, and subvolume of the first 
file name: this is true whether the first file name is fully qualified or is partially 
qualified by the default objsubvol.
[ ?SECTION ] 
 [ CONFIG [ FILE ] filename [ filename [ filename ] ] ]
 [ STARTUP [ PARAMS ] { YES | NO } ]
[ ?SECTION env-name 
 [ CONFIG [ FILE ] filename [ filename [ filename ] ] ]
 [ STARTUP [ PARAMS ] { YES | NO } ] ]
 .
 .
 .










