OSI/MHS Management Programming Manual

SPI Programming Considerations for OSI/MHS
OSI/MHS Management Programming Manual—424824-001
3-2
Definition Files
command interpreter always loads the entire definition file. For further information
about how definition files are used by an application, see the SPI Programming Manual.
Definition files are named according to the following convention:
subsys
is a three-character code identifying the subsystem or other software component to
which these definitions belong. This code is MHS for Compaq OSI/MHS.
The last characters of each file name denote the language in which the definitions in this
file are coded.
The files are located on the disk volume chosen by your site. The default disk volume
used by the INSTALL program is $SYSTEM.
An application that sends DSM commands to and receives responses from the OSI/MHS
subsystem needs the following definition files in the appropriate programming language:
•
The SPI (ZSPI) definition file
•
The common SPI extensions (ZCOM) definition file
•
The OSI/MHS (ZMHS) definition file
An application that retrieves event messages issued by the OSI/MHS subsystem needs
all the definition files listed above, plus the following:
•
The EMS (ZEMS) definition file
•
The operating system (ZGRD) definition file
•
The file-system (ZFIL) definition file
•
The common implementation of the SPI extensions (ZCMK) definition file
For example, a management application written in TAL that sends commands to and
retrieves event messages issued by the OSI/MHS subsystem would need the following
SOURCE statements:
?SOURCE ZSPIDEF.ZSPITAL
?SOURCE ZSPIDEF.ZCOMTAL
?SOURCE ZSPIDEF.ZMHSTAL
?SOURCE ZSPIDEF.ZEMSTAL
?SOURCE ZSPIDEF.ZGRDTAL
?SOURCE ZSPIDEF.ZFILTAL
?SOURCE ZSPIDEF.ZCMKTAL
ZSPIDEF.ZsubsysC
ZSPIDEF.ZsubsysCOB
ZSPIDEF.ZsubsysDDL
ZSPIDEF.ZsubsysTACL
ZSPIDEF.ZsubsysTAL