GDSX Management Programming Manual

Communicating With GDSX
GDSX Management Programming Manual—529930-001
2-2
Naming Rules and Guidelines for Applications
•
Data communications definition file
•
GDS definition file
If the application also communicates with other subsystems, then the definition files for
those other subsystems must also be used.
For example, a GDSX application written in COBOL85 that retrieves event messages
would require the following definition files:
These files are located on the disk volume chosen by your site.
For further information about the SPI definitions, EMS definitions, and data
communications definitions, see the SPI Programming Manual and the EMS Manual.
The GDS definitions are described in this manual.
Naming Rules and Guidelines for Applications
HP uses names beginning with the letter Z for all definitions and all component fields of
structures in its definition files. To avoid conflicts with names defined by HP, it is best
not to begin any names you define in your applications with uppercase or lowercase Z.
Common Syntax Elements for the GDS
subsystem
The token-oriented programmatic interface to GDSX consists of the following kinds of
syntax elements:
•
Commands and command numbers
•
Object types and object names
•
Event numbers
•
Subjects for event messages
•
Other tokens (tokens for parameters, results, and elements of an event message).
•
Constructs involving multiple tokens
•
Components of commands and responses
•
Components of an event message
The following paragraphs describe each kind of element and how it is used.
ZSPIDEF.ZSPICOB
ZSPIDEF.ZEMSCOB
ZSPIDEF.ZCOMCOB
ZSPIDEF.ZGDXCOB
SPI definitions
EMS definitions
Data communications definitions
GDS definitions