Pathway/iTS Management Programming Manual

Pathway/iTS Management Programming
NonStop Pathway/iTS Management Programming Manual—426749-002
2-5
Control and Inquiry
Control and Inquiry
To communicate with the PATHMON process through the Pathway management
programming interface, a management application must follow these steps:
1. Start a PATHMON process if one is not already running.
2. Open the PATHMON process.
3. Build a message to send to PATHMON.
4. Send the message to PATHMON.
5. Receive a response from PATHMON.
6. Decode the response.
7. Handle errors.
8. Take any appropriate actions.
9. Close PATHMON.
Information about starting, opening, and closing a PATHMON process appears in
TS/MP Management Programming Manual. Information on building and sending
messages, and receiving responses to them, appears in the following paragraphs.
Sending Commands and Receiving Replies
A management application uses the SPI procedures SSINIT, SSNULL, SSPUT,
SSPUTTKN, SSGET, SSGETTKN, SSMOVE, and SSMOVETKN to build a message
for the PATHMON process and to retrieve values from PATHMON’s response. (For
corresponding TACL procedures, see the SPI Programming Manual.)
The method you use to send and receive messages depends on the programming
language in which you write your management application. Message transport is part
of the language you use to program your requester; it is not part of SPI.
The management application also uses SPI to obtain event messages. The EMSGET
procedure extracts the elements (that is, tokens) of the messages, and the EMSTEXT
procedure obtains the text versions of the messages. For more information on event
management, see Section 9, PROG Commands and Section 10, Tell Message
Commands in this manual and see the EMS Manual.
Figure 2-1 on page 2-6 illustrates the commands sent and the responses received
when configuring a Pathway subsystem.