Section 7 Using Programmatic Interfaces; Overview Of Spi And Ems - HP TACL Programming Manual

Tandem advanced command language
Table of Contents

Advertisement

7 Using Programmatic Interfaces
Previous sections have described how to send textual commands to processes and
retrieve textual results. This section describes how to access two facilities, the
Subsystem Programmatic Interface (SPI) and the Event Management Service (EMS),
that provide a programmatic interface for managing:
SPI and EMS are considered to be programmatic interfaces because information is
represented by coded values, called tokens, which are easier for programs to
manipulate than textual commands and results.
This section does not provide detailed information about SPI or EMS; it does, however,
show how to use TACL to communicate with SPI and EMS. For additional
information, see the Introduction to Distributed Systems Management (DSM), the
Distributed Systems Management (DSM) Programming Manual, and the Event
Management Service (EMS) Manual.
Overview of SPI and
SPI and EMS are two components of the Distributed System Management (DSM)
EMS
product group, a set of software applications, tools, and services that facilitates
management of systems and networks:
107365 Tandem Computers Incorporated
Operating system utilities
Tandem products such as Pathway, the TMF subsystem, and SNAX (also known
as subsystems)
Other applications that support these interfaces
SPI is a set of procedures, associated definition files, and programming
conventions used for building, sending, retrieving, and decoding messages sent
between management applications and the Tandem subsystems or business
applications they manage. SPI makes possible the programmatic equivalent of an
interactive command interface, allowing you to automate management tasks. The
following diagram shows how applications interact with SPI:
Operations Environment
Management
Applications
EMS is a set of processes, associated definition files, tools, and programming
conventions that provides event-message collection, logging, and distribution for
the operating system. (An event is a significant change in some condition in the
system or network, such as a device failure, a notification of limits exceeded, or a
SPI
Subsystem Environment
Tokenized
Messages
Subsystems
or
Applications
Objects
322
7–1

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents