Spi Programming Considerations; Definition Files - HP NonStop Pathway/iTS Programming Manual

3

SPI Programming Considerations

After your subsystem and EMS processes are running and your management
application has established communication with the Pathway subsystem, the main
business of your management application is to format and send commands, decode
responses and act on the results, and interpret event messages and act on their
information.
This section provides summary information about SPI programming and discusses SPI
programming considerations specific to the Pathway subsystem. Topics included are:

Definition Files

Message Elements for the Pathway Subsystem
Building and Sending a Command Message
Receiving and Decoding Response Messages
Event and Error Handling
Security on page 3-31
Retrieving and decoding event messages
Templates
Naming Guidelines for Applications
Programming Considerations for Specific Object Types
Writing C Programs
Command Presentation
For a complete list of all token codes and token maps specific to the Pathway
subsystem, see the ZSPIDEF.ZPWYDDL file.
Definition Files
The commands, responses, and event messages sent to and received from the
Pathway subsystem are made up of items called "tokens." Each token contains a
particular piece of information, such as a command parameter or an item of information
about an event. Tokens can be single values or structures consisting of several values.
Some tokens, called "header tokens," are present in every command and response
and in every event message.
Tokens and related data items for commands, responses, and event messages must
be declared in your management applications. HP provides these declarations for you
in definition files. A set of definition files is provided as part of each HP NonStop
subsystem that supports DSM. A few other NonStop software components (such as
NonStop Pathway/iTS Management Programming Manual—426749-002
on page 3-28
on page 3-31
on page 3-34
on page 3-35
3 -1
on page 3-4
on page 3-19
on page 3-27
on page 3-32