Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

Mixed Network Requirements
1-14
109759—Distributed Systems Network Management (DSNM) Subsystem Interface
Development Guide
Overview of DSNM
To run concurrent copies with no DSNM configuration, use the standard names and
change only the process prefix character.
If you are running DSNM under NonStop NET/MASTER MS, no special configuration
is required. DSNM processes take their process prefix character from the first character
of the NonStop NET/MASTER NCP process (refer to the NonStop NET/MASTER MS
System Management Guide for more information).
If you are running DSNM as a PATHMON-controlled application, you must create a
separate PATHMON configuration for each concurrent copy of DSNM you wish to run.
Refer to the Distributed Systems Management Solutions (DSMS) System Management
Guide for more information on running multiple copies of DSNM.
Mixed Network Requirements
DSNM can operate in a network that includes systems running both C-series and
D-series versions of the Tandem Nonstop operating system. In such a mixed network,
the DSNM modules that access remote files or processes must run at low PINs
(processor identification numbers). All DSNM modules are released with the HIGHPIN
parameter set to OFF.
Refer to the Distributed Systems Management Solutions (DSMS) System Management
Guide and the documentation that accompanies your site update tape (SUT) for
information on system configuration and these DSNM modules.
Extending DSNM Support
Suitable subsystems can be added to the existing base of DSNM-managed subsystems in
a modular way, without modifying existing subsystem support, by providing an I process
and an E process for the targeted subsystem.
The remainder of this manual describes the development of I processes.