Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

SUBSYSTEM Class Records
6-8
109759—Distributed Systems Network Management (DSNM) Subsystem Interface
Development Guide
Configuring a New Subsystem Into DSNM
[NOT] RESOLVE-SUBOBJ-WITHOUT-DNS
indicates whether the subordinate object is unique within a subsystem, and it is
not necessary for DNS object name resolution.
[NOT] DUMMY-DNS-MGR
[NOT] DUMMY-DNS-MANAGER
[NOT] MGR-IN-DNS-IS-DUMMY
[NOT] MANAGER-IN-DNS-IS-DUMMY
indicates whether a manager name in DNS for the subsystem is used only to
determine the Tandem node on which the object is located. The DNS manager
name is ignored.
Default: All flags default to the NOT condition.
MANAGER
MANAGER is the unqualified file name of the subsystem manager program file, if the
subsystem uses a manager of which multiple instances can be run.
This parameter is used by the command server to assist name resolution. The command
server attempts to determine the subsystem of an object by comparing the file name of
the manager process to this parameter value when the manager is given in a command
but the subsystem is not.
The MANAGER parameter is not used to control or access the manager process.
Default: None.
Considerations: Only the file name is needed, not its node, volume, or subvolume. For
example, specify “PATHMON” for “$SYSTEM.SYSTEM.PATHMON.”
When this form is used for automation-I-supported subsystems, the *-MGR-REQ and
MGR-REQUIRED flags must be set (FLAGS parameter), and the UNDER $manager
qualifier is required in the DSNM command syntax. You must also include CI-CONFIG
class records to define the control interface process.
Note. If you modify the MANAGER parameter, you must also modify the CI-CONFIG class,
OBJECT-FILE parameter accordingly, if it exists.
Class Component Parameter Value Formats
SUBSYSTEM subsystem MANAGER unqualified-filename