OSI/MHS Management Programming Manual

Communicating with the OSI/MHS Processes
OSI/MHS Management Programming Manual—424824-001
2-3
Running the OSI/MHS Subsystem Processes
All base-group tokens appear in the first segment, and are not repeated in later segments
of the record.
Each instance of the repeating group is enclosed in a segment list, which starts with
ZSPI-TKN-SEGLIST and ends with ZSPI-TKN-ENDLIST. Segment lists follow the
base-group tokens. A segmented response always contains at least one segment list
(which is empty if the server has no information to return).
If a segment does not complete a response record, it contains ZSPI-TKN-MORE-DATA
with a value of TRUE, indicating that more segment lists are available. The message
containing this segment also contains ZSPI-TKN-CONTEXT so the requester can
follow the standard protocol for continuing the response. (See the SPI Programming
Manual.)
ZSPI-TKN-MORE-DATA does not appear in the last segment, indicating that this
segment completes the response record.
Requesting a Segmented Response
To request a segmented response, a command must include ZSPI-TKN-ALLOW with
the value ZSPI-VAL-ALLOW-SEGMENTS. Otherwise, segmentation is disallowed.
You must allow or disallow segmented responses for each command you issue. The
default is to disallow segmented responses.
For a complete discussion of response segmentation, see the SPI Programming Manual.
Running the OSI/MHS Subsystem Processes
Before your management application can send commands to Compaq OSI/MHS through
SCP, you must first install OSI/MHS. Installation of OSI/MHS includes creation of the
required databases. For instructions, refer to the section on installation in the OSI/MHS
Configuration and Management Manual.
After the OSI/MHS subsystem is installed, you can run the MHS manager. The MHS
manager accepts commands and options through SCF, PARAM messages, and options
at run time. The SCF commands are described in the OSI/MHS SCF Reference Manual.
The PARAM messages, the RUN command options, and examples of these two
methods are described in the section on starting, stopping, and updating in the OSI/MHS
Configuration and Management Manual.
Running an EMS Consumer Distributor
Before your application can retrieve event messages and accounting messages generated
by OSI/MHS, you must start an Event Management Service (EMS) consumer distributor
process. A consumer distributor returns selected event messages to a requesting
Note. OSI/MHS processes run only at low PINs. If those processes interact with processes
that run at high PINs—for instance, if a GPI or OSI/AS process runs at a high PIN—the high
PIN process must be named. For details on this and related topics, see the D-Series System
Migration Planning Guide. For information about running OSI/AS at a high PIN, see the
OSI/AS Configuration and Management Manual.