TS/MP 2.5 Release Supplement

Figure 5 SCF Management Interface for ACS Subsystem
The SCF process determines which subsystem runs the command (the ACS subsystem in this case).
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 run any ACS specific SCF commands.
The SCP process (system default name $ZNET) enables an SCF process to monitor and control the
ACS subsystem by communicating with the domain coordinator process, which is a NonStop
process pair that manages event communication within the local system and is the boot process
for the ACS subsystem.
The Subsystem Programmatic Interface (SPI) messages support communication between the SCP
and the ACS subsystem.
Supported Commands
This subsection includes the following topics:
• “List of ACS Subsystem-specific Commands” (page 63)
• “Syntax Help for SCF Commands” (page 64)
List of ACS Subsystem-specific Commands
Most ACS subsystem commands are valid only for specific states, as shown in Table 8 (page 64).
The table also lists the ACS subsystem commands that are SCF-sensitive and SCF-non-sensitive.
Supported Commands 63