TR3271 Management Programming Manual

ELEMENTS OF SPI MESSAGES FOR THE SUBSYSTEM
The commands sent to the subsystem and the responses and event
messages received from the subsystem are made up of tokens.
The concept of tokens is described in the Distributed Systems
Management Manual . See Section 5, "Common Definitions," in this
manual for an explanation of tokens present in multiple commands,
responses, or event messages for the TR3271 subsystem.
This manual does not attempt to give a complete explanation
of tokens; it provides subsystem-specific information about the
tokens used to communicate with the TR3271 subsystem. General
information about tokens can be found in the Distributed Systems
Management (DSM) Programming Manual , and information about tokens
common to all data-communications subsystems can be found in the
Communications Management Programming Manual .
DEFINITION FILES
Definition files supplied by Tandem provide declarations of
commonly needed tokens and other variables, as well as structures
and values. The declaration names in these files have a standard
form that identifies the definition file they come from and
what the declaration defines. In addition, each source of
definitions, such as the TR3271 subsystem or SPI, has associated
with it a set of five definition files: one in TAL, one in
COBOL85, one in TACL, one in C, and one in DDL. The definition
files in TAL, COBOL85, and TACL are derived from the definition
file in DDL.
To include the definition files in your management application,
use the mechanism that is appropriate for the programming
language in which the application is written. Some of the
mechanisms are as follows:
• In TAL, source in the definition files using ?SOURCE compiler
directives.
• 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 to enable COBOL85 programmers to declare multiple copies
of structures in the definition file. When programming in TAL,
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 .
3-2