OSI/TS Management Programming Manual
Programmatic Commands
Introduction
056786 Tandem Computers Incorporated 1–5
5. An application installs an EMS filter specifying the selection of event messages it
wants to receive. (Filters are optional but recommended. If no filter is installed,
all event messages will be delivered to the application.)
6. The application opens an EMS consumer distributor and requests an event
message.
7. The distributor reads the log and returns to the application the next event message
that satisfies the conditions of the filter.
8. The application either presents the message to the operator or takes action itself.
Programmatic
Commands
Like all other subsystems that support DSM, OSI/TS defines a set of object types—the
kinds of objects that can be managed by OSI/TS—and a set of commands that can be
performed on objects of these types.
Object Types The OSI/TS object types are:
PROCESS
SERVICE
SU
ROUTE
In addition, a null object type is provided for those commands that do not require
specification of a particular object type.
PROCESS
A PROCESS object is one of the processes that make up OSI/TS or one of its
supporting subsystems.
SERVICE
A SERVICE object is a set of default values for protocol configuration parameters,
thresholds, and statistics within the Network Layers and Transport Layers of your
OSI/TS subsystem. There are two SERVICE objects for OSI/TS:
The L3 SERVICE, for Network Layer protocol parameter values
The L4 SERVICE, for Transport Layer protocol parameter values
You can change a SERVICE object, but you cannot add or delete a SERVICE object.
SERVICE objects define configurations that affect all connections within their
respective layers.
SU
An SU (subdevice) object is a logical entity that provides access to a transport
connection. There are two types of SUs: static and dynamic. A static SU object is
temporary, it is added dynamically at connection establishment time, and lasts only as
long as the connection exists. A dynamic SU object is saved when the connection is
finished and can be reused by another connection if that connection desires the same