TCP/IP TELNET Management Programming Manual
Definition Files
Elements of SPI Messages for the TELNET Subsystem
3–2 53474 Tandem Computers Incorporated
To include the definition files in your management application, use the mechanism
appropriate for the programming language in which the application is written. The
appropriate mechanisms are as follows:
In TAL or C, source-in the definition files
In COBOL85, copy the definition files into your program using COPY statements.
In TACL, load the definition files using LOAD commands.
The definitions in a COBOL85 definition file are grouped into sections. This grouping
enables COBOL85 programmers to declare multiple copies of structures in the
definition file. When programming in TAL or C, always source-in the entire definition
file, and; when using TACL, always load the entire file. For further information on
how a management application accesses definition files, refer to the Distributed Systems
Management (DSM) Programming Manual.
A management application that communicates with the TELNET subsystem must
include the following definition files, where xxx represents one of five specific
abbreviations for COBOL85, TAL, C, TACL, or DDL and corresponds to the
programming language that the application is written in, and sss represents a
subsystem identifier:
The SPI definition file, ZSPIDEF.ZSPIxxx.
The EMS definition file, ZSPIDEF.ZEMSxxx. This definition file is needed only if
the application retrieves event messages or controls EMS.
The data communications definition file, ZSPIDEF.ZCOMxxx.
The TELNET definition file, ZSPIDEF.ZTNTxxx.
If the application communicates with other subsystems, the definition file
ZSPIDEF.Zsssxxx for each of the other subsystems.
Here is an example of the definition files needed by a TELNET application written in
TAL that retrieves event messages:
ZSPIDEF.ZSPITAL SPI definitions
ZSPIDEF.ZEMSTAL EMS definitions
ZSPIDEF.ZCOMTAL Data communications definitions
ZSPIDEF.ZTNTTAL TELNET definitions
These files are located on the disk volume chosen by your site. The default disk
volume used by the INSTALL program is $SYSTEM.
Section 5, “Common Definitions,” lists the SPI, EMS, and data communications
standard definitions used by the TELNET subsystem. For detailed descriptions of the
SPI standard definitions, refer to the Distributed Systems Management (DSM)
Programming Manual; for the EMS standard definitions, refer to the Event Management
Service (EMS) Manual; and for the data communications standard definitions, refer to
the Communications Management Programming Manual. In this manual, the declarations
in the TELNET definition files are described in Section 5, “Common Definitions.”