TS/MP Supplement for Limits Relief (H06.05+, J06.03+)

START
Use the START command to start the ACS subsystem. The START command reads the
configuration values stored in the BCINI file and begins the process of starting the subsystem.
When the subsystem successfully completes processing this command, ACS subsystem
processes are available in each processor in the system.
Note: Before issuing this command, you must start the domain coordinator process
($ZACS).
1.
If your application environment uses Pathsend requesters, you must start the
ACS subsystem before you start the PATHMON process.
2.
This is a sensitive command.
Syntax Summary.
START [ /OUT file-spec/ ] [ object-spec ]
Syntax Descriptions.
OUT file-spec
specifies a file for the output of this command. The file can be on the same physical
system as the ACS subsystem or on any system in the same Expand network.
object-spec
specifies the name of the object. The fully qualified object-spec has the format:
[ ACS ] [ system-name.]$ZACS
system-name is the physical, Guardian name of the system in which the object is
being added and configured.
If you specify the SCF object type (ACS) or any portion of the object name (
acs-spec) in a prior ASSUME command, you can omit it in this command. For
information about the ASSUME command, see the SCF Reference Manual for G-Series
RVUs or the SCF Reference Manual for H-Series RVUs.
If you have not used a prior ASSUME command and you omit system-name, the
command defaults to the local physical system.
Usage Note.
The START command initiates the process of starting the ACS subsystem. In the background,
$ZACS performs all the tasks necessary to start the ACS subsystem. Because START is a
no-waited command, use the STATUS command to track the progress of the START command.
Examples.
The following START command initiates the process of starting the ACS subsystem on the