Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

Distributed Systems Network Management (DSNM) Subsystem Interface Development
Guide—109759 3-1
3
I Process Development Process
Scope of This Section
This section introduces the conceptual model upon which the I process program’s frame
and command thread interactions and supporting library services are based. Also
provided are a detailed development model and associated rules for using the I process
development software correctly and effectively.
The purpose of this section is to:
•
Define central concepts of the I process program structure.
•
Describe the environment and services provided for I process development, focusing
on the command thread and how it interacts with the program frame and library
services.
•
Outline how to integrate your code with the frame code to produce a working
I process.
Complete syntax and parameter descriptions for all procedures, literals, defines, and
structure templates discussed in this section are provided in Appendix A, “DSNM
Library Services.” ZDSN error codes are described in Appendix B, “DSNM Error
Codes.” The SPI DDL constants and structure definitions that users must know about
are listed in Appendix C, “Data Definition Language (DDL)-Defined DSNM SPI
Components.”
Function of the I Process
You add a Tandem or customer-written subsystem to the existing base of DSNM-
managed subsystems by providing a DSNM subsystem interface process, commonly
referred to as an “I process.” An I process converts DSNM commands affecting
subsystem objects into a sequence of subsystem commands, sends them to the targeted
subsystem’s control interface for processing, and converts the result into a standard
DSNM form.
An I process is a member of a DSNM server class. As highlighted in Figure 3-1, it:
•
Receives commands from a DSNM requester (usually the command server).
•
Converts DSNM commands into syntactically correct subsystem commands.
•
Presents commands to the subsystem CI for execution.
•
Converts the result into a standard DSNM form.
•
Returns responses to the requester.
Note. Appendix D, “Sample I Process Program Code,” contains an example of the user-written
portion of an I process program, illustrating the model and associated library services
described in this section. You may find it helpful to refer to this sample code when reading this
section.