GDSX Management Programming Manual

Introduction
GDSX Management Programming Manual—529930-001
1-2
How Applications Fit Into the GDSX Architecture
•
It is efficient to transfer as many routine management tasks as possible on to the
computer system or network itself. Doing this frees the operators and other
personnel to do the work that requires judgment and creativity.
•
Information obtained through the programmatic interfaces can be used directly by
an application to control its actions, produce reports, and so forth.
An application that uses the control-and-inquiry and event-management interfaces can
perform tasks that once required the use of two or three interactive interfaces, and
such an application can also communicate with multiple subsystems. In addition, the
capability to write your own applications allows you to tailor them to the needs and
configuration of your system.
You could, for example, write an application that uses the control-and-inquiry interface
to check the number of errors occurring on all the GDSX lines in the system and stop
lines that have too many errors. An application could monitor the events occurring in
GDSX and react to the notification that a line is going down by starting another line to
handle the traffic.
How Applications Fit Into the GDSX
Architecture
An application uses the control-and-inquiry interface to the GDS subsystem by sending
commands to and receiving responses from the Subsystem Programmatic Interface
(SPI), which in turn uses the Subsystem Control Point (SCP). An application uses the
Event Management Service (EMS) to retrieve event messages generated by the GDS
subsystem by sending commands to and receiving responses from an EMS distributor
process.
Figure 1-1 illustrates how an application fits into the architecture of GDSX.