TR3271 Management Programming Manual

ELEMENTS OF SPI MESSAGES FOR THE SUBSYSTEM
Definition Files
A management application that communicates with the TR3271
subsystem must include the following definition files in the
appropriate programming language, where xxx represents one of
four specific abbreviations for COBOL85, TAL, TACL, C, or DDL and
subsys represents a subsystem identifier:
• The SPI definition file, ZSPIDEF.ZSPI xxx .
• The EMS definition file, ZSPIDEF.ZEMS xxx . This definition
file is needed only if the application retrieves event
messages or controls its EMS distributor environment
• The data-communications definition file, ZSPIDEF.ZCOM xxx .
• The TR3271 definition file, ZSPIDEF.ZTR3 xxx .
• If the application communicates with other subsystems, the
definition file ZSPIDEF.Z subsysxxx for each of the other
subsystems must also be included.
An example of the definition files needed by an TR3271 applica-
tion written in COBOL85 that retrieves event messages is as
follows:
ZSPIDEF.ZSPICOB SPI definitions
ZSPIDEF.ZEMSCOB EMS definitions
ZSPIDEF.ZCOMCOB Data-communications definitions
ZSPIDEF.ZTR3COB TR3271 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 TR3271 subsystem.
For detailed descriptions of these standard definitions, refer
to the Distributed Systems Management (DSM) Programming Manual ,
the Event Management Service (EMS) Manual , and the Communications
Management Programming Manual , respectively. The declarations in
the TR3271 definition files are described in this manual and are
listed in Appendix B.
NOTE
This manual uses DDL to describe all tokens. For a quick
explanation of DDL, refer to the appendix "Overview of
DDL for SPI" in the Distributed Systems Management (DSM)
Programming Manual . If you are programming in TAL or TACL,
substitute a circumflex (^) for each hyphen in a definition
name as it appears in this manual. For example, ZCOM-OBJ-
SU becomes ZCOM^OBJ^SU in TAL and TACL.
3-3