OSI/TS Management Programming Manual

Definition Files
SPI Programming Considerations for OSI/TS
3–2 056786 Tandem Computers Incorporated
Definition files are named according to the following convention:
ZSPIDEF.Z subsys TAL
ZSPIDEF.Z subsys COB
ZSPIDEF.Z subsys C
ZSPIDEF.Z subsys TACL
ZSPIDEF.Z subsys DDL
ZSPIDEF.Z subsys P
subsys
is a three-character code identifying the subsystem or other software component to
which these definitions belong. This code is OS4 for Tandem OSI/TS.
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/TS
subsystem needs the following definition files in the appropriate programming
language:
The SPI (ZSPI) definition file
The data communications (ZCOM) definition file
The OSI/TS (ZOS4) definition file
An application that retrieves event messages issued by the OSI/TS subsystem needs
all the definition files listed above, plus the following:
The EMS (ZEMS) definition file
The Guardian 90 (ZGRD) definition file
The file-system (ZFIL) definition file
For example, a management application written in TAL that sends commands to and
retrieves event messages issued by the OSI/TS subsystem would need the following
SOURCE statements:
?SOURCE (ZSPIDEF.ZSPITAL)
?SOURCE (ZSPIDEF.ZCOMTAL)
?SOURCE (ZSPIDEF.ZOS4TAL)
?SOURCE (ZSPIDEF.ZEMSTAL)
?SOURCE (ZSPIDEF.ZGRDTAL)
?SOURCE (ZSPIDEF.ZFILTAL)