Pathway/iTS Management Programming Manual

SPI Programming Considerations
NonStop Pathway/iTS Management Programming Manual—426749-002
3-3
Location
•
Token numbers, which uniquely identify each token
•
Token codes, used in defining simple tokens
•
Predefined values
•
Token maps, used to reference extensible structured tokens
•
Error numbers
•
Subsystem ID definition
•
Message buffer declaration
•
Event tokens
•
Building blocks, which are definitions that appear at the beginning of a definition
file and are referenced by TYPE clauses that appear later in the file. Building
blocks are present in ZPWYDDL, but are not generated for ZPWYC, ZPWYTAL,
ZPWYCOB, or ZPWYTACL.
Location
The files are located on the disk volume chosen by your site. The default disk volume
used by the Install program or the Distributed Systems Management/Software
Configuration Manager (DSM/SCM) utility is $SYSTEM.
Which Files Do You Need?
An application that sends DSM commands to and receives responses from the
Pathway subsystem needs the following definition files in the appropriate programming
language:
SPI (ZSPI) definition file
PWY (ZPWY) definition file
An application that retrieves event messages issued by the Pathway subsystem needs
the following definition files:
SPI (ZSPI) definition file
PWY (ZPWY) definition file
EMS (ZEMS) definition file
For example, a management application written in COBOL that sends commands to
and retrieves event messages issued by the Pathway subsystem would copy or load
the following definition files:
ZSPIDEF.ZSPICOB
ZSPIDEF.ZPWYCOB
ZSPIDEF.ZEMSCOB
If your application manages subsystems other than Pathway, it also needs the
definition files required by those subsystems. For instance, you might want your
Pathway management application to manage an associated TMF subsystem as well. If