TS/MP Supplement for Limits Relief (G06.26+)

chapter describes the SCF commands that are interpreted specifically for ACS. The SCF
Reference Manual for G-Series RVUs provides general information about SCF commands. You
should be familiar with that information before reading the ACS subsystem-specific
information provided here.
Architecture
As shown in Figure 7-1, the SCF interface locates and communicates with the appropriate
product module, in this case ACSPM. SCF provides an operational interface to an intermediate
process, the Subsystem Control Point (SCP), which in turn communicates with the domain
coordinator process. The domain coordinator is run as a NonStop process pair, which is
maintained by the persistent manager process $ZPM that provides the Subsystem Programmatic
Interface (SPI) to support the SCF commands.
Figure 7.1. SCF Management Interface for ACS Subsystems
The SCF process determines which subsystem executes the command (which is the ACS
subsystem in this case) then it launches the product module responsible for that subsystem (for
example, ACSPM for the ACS subsystem) and forwards the command to that product module.
The domain coordinator ($ZACS) processes the commands; the ACS product module parses the
commands specific to the ACS subsystem and formats the display of results. The domain
coordinator process must be started before you can execute any ACS-specific SCF commands.
The SCP process (system default name $ZNET) enables an SCF process to monitor and control
an ACS subsystem by communicating with the domain coordinator process, which is a process
pair that manages event communication within the local system and is the boot process for the
ACS subsystem.