Distributed Name Service (DNS) Management Programming Manual

Definition Files
SPI Programming Considerations for DNS
3–2 46958 Tandem Computers Incorporated
Definition files are named according to the following convention:
ZSPIDEF.Z subsys C
ZSPIDEF.Z subsys COB
ZSPIDEF.Z subsys DDL
ZSPIDEF.Z subsys TACL
ZSPIDEF.Z subsys TAL
subsys
is a three-character code identifying the subsystem or other software component to
which these definitions belong. This code is DNS for Tandem DNS.
The last characters of each file name denote the language in which the definitions in
the 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 DNS
subsystem needs the following definition files in the appropriate programming
language:
The SPI (ZSPI) definition file
The DNS (ZDNS) definition file
An application retrieves event messages issued by the DNS subsystem needs 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 sends commands to and
retrieves event messages issued by the DNS subsystem would need the following
SOURCE statements:
?SOURCE ZSPIDEF.ZSPITAL
?SOURCE ZSPIDEF.ZDNSTAL
?SOURCE ZSPIDEF.ZEMSTAL
?SOURCE ZSPIDEF.ZGRDTAL
?SOURCE ZSPIDEF.ZFILTAL
Likewise, a management application written in C that sends commands to and
retrieves event messages issued by the DNS subsystem would need the following
include statements:
#include "zspidef.zspic"
#include "zspidef.zdnsc"
#include "zspidef.zemsc"
#include "zspidef.zgrdc"
#include "zspidef.zfilc"