Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

Distributed Systems Network Management (DSNM) Subsystem Interface Development
Guide—109759 6-1
6
C
onf
DSNM
Scope of This Section
This section contains the steps necessary to configure a subsystem and its associated
I process into DSNM. More configuration and management details, including an
extended list of the DSNM process class configuration parameters, can be found in the
Distributed Systems Management Solutions (DSMS) System Management Guide.
As an I process developer, you must provide the person responsible for installing and
managing DSNM at your site with configuration information specific to your I process,
the subsystem(s) it manages, and the subsystem manager process (CI) with which it
communicates.
New and Changed DSNM Configuration Information
DSNM now runs “out-of-the-box,” which means DSNM can execute without
customization after the Install REPSUBSYS phase. DSMS processes use internal
default values that previously had to be specified in various configuration files. All user-
supplied configuration files are optional, and the post-Install function (DINSTALL) has
been eliminated.
Note the following important highlights of the DSNM customization changes:
•
By default, DSMS now operates with most files in a single subvolume (the ISV or a
copy of the ISV) rather than being distributed among several subvolumes as in
previous releases.
•
DSMS now creates the object database if it does not exist.
•
$SYSTEM.SYSTEM.ZDSNCONF is a new file (since the C31 release) and is
installed by the REPSUBSYS phase of the Install program. This file is a key-
sequenced file and contains DSNM configuration parameters supplied by Tandem.
$SYSTEM.SYSTEM.ZDSNCONF may change at each release, but you should not
alter it yourself. If you need to override particular parameters for your installation,
refer to the Distributed Systems Management Solutions (DSMS) System
Management Guide.
•
The $SYSTEM.SYSTEM.DSNM file is no longer a required file.
Note. For testing purposes, it is convenient to maintain all of your subsystem, CI, and
I process configuration records in a separate configuration file. If you compile in test mode,
you can then run your I process with the TESTMODE and CONFIG process parameters to
specify this file.
Note. Verify that your system is updated to the C30 DSMS release before installing C31 or a
later release. The C30 DSMS release contained major changes in the handling of DSMS
process and file names.