Safeguard Management Programming Manual (G06.29+, H06.08+, J06.03+)

Communicating With the Subsystem
Safeguard Management Programming Manual—422086-028
3-2
Definition Files
all the SMON processes with a priority of 199. The Safeguard software also creates
audit files when they are needed.
Definition Files
A Safeguard management application program must refer to several definition files.
These files are defined for SPI, the Event Management System (EMS), the Subsystem
Control Point (SCP), data-communications subsystems, and the Safeguard subsystem.
The standard data types, token codes, token maps, token structures, constants,
values, and other definitions used with SPI are contained in these files.
HP provides the SPI standard definitions in files of source declarations in DDL and in
the programming languages that support Distributed Systems Management (DSM):
TAL, C, Pascal, COBOL, and TACL. They consist of six definition files––one in each
language plus the DDL definition file.
Similarly, each subsystem or management process (including SCP) supports a
programmatic command interface based on SPI that reports events through EMS, or
that defines SPI error lists, also provides six definition files––one per language plus the
DDL definition file. For SPI and for each subsystem, the files for all the programming
languages are generated by the DDL compiler from the DDL file.
To use definitions from a particular source, your Safeguard management application
program must load the definition file associated with the source command in the
appropriate programming language.
The definitions in a TAL, C, Pascal, or COBOL definition file are grouped into sections,
so that only definitions that are needed are included in the application. For TACL, the
entire definition file must be used. For more information about, how definition files are
accessed by application, see the SPI Programming Manual.
Writers of Safeguard management applications that use SPI must use the
programming language version of each definition file:
•
The ZSPI file, which contains the standard SPI definitions.
•
The ZEMS file, which contains the standard EMS definitions (if your application
retrieves event messages).
•
The ZCOM file, which contains the standard data communications definitions.
•
The ZSFG file, which contains definitions for the Safeguard software. (The ZSFG
files may contain some definitions that are currently not implemented.)
•
The ZCMK file, which contains some common definitions.
Note. The Safeguard SPI allows for, but does not require, the use of the Subsystem Control
Point (SCP) process as the gateway to the programmatic interface. Thus, Safeguard SPI
follows SCP implementation standards and uses the SCP ZCOM enumerated values for
commands, object types, and some common errors.