Table of Contents
Advertisement
MANAGEMENT PROGRAMMING FOR TR3271
Communicating With the TR3271 Subsystem
The management application retrieves event messages by sending
commands in SPI message format to an EMS consumer distributor.
To select event messages, you can write a filter that is specific
to your needs.
If no filter is used, all event messages in
the log file are passed to the management application by the
consumer distributor.
Figure 2-1 illustrates the flow of data
between the TR3271 subsystem and a management application in the
EMS environment.
For detailed descriptions of event messages
and event management as they relate to the TR3271 subsystem,
refer to Section 7, "Event Management."
For a description of
event messages and event management in general, refer to the
Event Management Service (EMS) Manual .
Note that an operator can
monitor event through VIEWPOINT.
Reffer to the VIEWPOINT Manual
for details.
COMMUNICATING WITH THE TR3271 SUBSYSTEM
A management application communicates with the TR3271 subsystem
by means of SCP or the EMS distributor process.
When communicat-
ing with SCP or EMS, an application calls SPI procedures to
build messages to be sent to the subsystem and to retrieve
messages sent from the subsystem.
However, to send and receive
SPI messages, and to establish and terminate communication with
SCP or the EMS distributor process, an application must use the
GUARDIAN 90 file system.
How you use the GUARDIAN 90 file system
depends on the language in which your application is written.
If your application is written in TAL, you use the file-system
procedures directly to send and receive the SPI messages.
If
your application is written in COBOL85--COBOL 74 does not support
SPI--you use the file-system procedures indirectly by invoking
them through COBOL85 verbs.
If your application is written in
TACL, you use the file-system procedures indirectly by invoking
them through TACL built-ins.
2-11
Advertisement
Table of Contents
