Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

The Subsystem Layer
1-10
109759—Distributed Systems Network Management (DSNM) Subsystem Interface
Development Guide
Overview of DSNM
•
The conversational interface processes (CIP), which provides access to
conversational utilities. It creates and terminates utility processes and emulates a
terminal from the utility’s point of view.
•
An event monitoring process (E process) for each supported subsystem provides the
interface between the targeted subsystem and the DSNM object monitoring services.
The E processes:
•
Forward state change information from the EMS distributor process to the object
monitor process.
•
Update state change information and other operational statistics in the object
database.
•
Rebuild the object data base after system reconfiguration.
The Subsystem Layer
The subsystem layer, an example of which is shown in Figure 1-3, comprises the
subsystems managed by the network-management application. This layer includes the
subsystem control interface processes (CIs) and the subsystem resources.
Control Interface Processes (CIs)
Subsystems support control and inquiry through their CI processes. In this manual, the
term “CI” is used in the general sense, to mean any gateway to the subsystem for control
and inquiry.
A CI is typically a management process such as PATHMON (the NonStop TS/MP
control process); a public interface management process such as the SCP
communications control facility, which further communicates with a private or
privileged subsystem manager process to actually execute commands; or possibly a set
of procedure calls such as are available for the Spooler.
A CI may execute as a server such as PATHMON or SCP, or as a requester such as PUP.
Requester CIs generally have a textual interface; servers variously use text, formatted
messages, or the subsystem programmatic interface (SPI).
Note. This release of the DSNM subsystem interface development software addresses
server-type CIs only.