Envoy ACP/XF Configuration and Management Manual

Subsystem Control Facility (SCF) for EnvoyACP/XF
EnvoyACP/XF Configuration and Management Manual—429232-003
4-4
Subsystem Control Point (SCP)
Figure 4-2 shows the relationships between DSM and the subsystem environment.
SCF is a DSM tool in the operations environment. It is a unified command interface
that simplifies the tasks of configuring, controlling, and collecting information about HP
subsystems.
When you use SCF, you can choose either to let a person perform an action (through a
terminal) or to automate that action through a command (OBEY) file. SCF returns
display and error-message output to a terminal or to a log file. Figure 4-1 shows these
communications.
The management services depend on the Subsystem Programmatic Interface (SPI) for
communication between the operations and subsystem environments. SPI is a
standard set of procedures and associated definition files that define common,
message-based, programmatic interfaces for communication between requesters and
servers—for instance, in a management application. SPI includes procedures to build
and decode specially formatted messages.
Subsystem Control Point (SCP)
As Figure 4-1 shows, SCF communicates with subsystems through the Subsystem
Control Point (SCP). SCP is an intermediate process that receives commands from
SCF and distributes them to subsystems. The default SCP process name is $ZNET.
The Subsystem Programmatic Interface (SPI) controls the programmatic
communications. SPI builds and retrieves information from command, response, and
event-message buffers.
SCP and SCF can reside on different nodes; however, these nodes must be
connected. SCP and the EnvoyACP/XF process must reside on the same node.
Figure 4-2. Overview of DSM Architecture
VST026.vsd
Subsystem Programmatic Interface (SPI)
DSM
Tools
Operators
Management
Applications
DSM
Applications
Operations
Environment
Management
Services
DSM
Services
Subsystem
Environment
Tandem
Subsystems
Business
Applications
Objects
Objects