TS/MP 2.5 Release Supplement

Table 8 SCF Commands for ACS Subsystems
Valid in These StatesSCF Non-sensitiveSCF SensitiveCommand
UNKNOWN—XADD
DEFINED, STOPPED—XALTER
STARTED—XCONTROL
DEFINED, STOPPED—XDELETE
UNKNOWN, DEFINED, STARTING, STARTED, STOPPING,
STOPPED
X—INFO
UNKNOWN, DEFINED, STARTING, STARTED, STOPPING,
STOPPED
X—NAMES
DEFINED, STOPPED—XSTART
STARTEDX—STATS
UNKNOWN, DEFINED, STARTING, STARTED, STOPPING,
STOPPED
X—STATUS
STARTING, STARTED—XSTOP
UNKNOWN, DEFINED, STARTING, STARTED, STOPPING,
STOPPED
X—VERSION
SCF sensitive commands can change the state or configuration of subsystem objects. Therefore,
the use of sensitive commands is restricted to users with special qualifications. For the ACS
subsystem, sensitive commands can be run only by members of the super ID (group ID 255).
Other SCF commands are non-sensitive, they request various kinds of information but do not affect
operation. These commands can be issued by all users.
Syntax Help for SCF Commands
To display the syntax for any SCF command supported by the ACS subsystem, use the HELP
command, as follows:
HELP ACS [ command ] [ object-type ]
where:
is the ACS subsystem-specific command name.command
is the object type, which is always ACS for ACS subsystems.object-type
For more information on the SCF HELP command, see the SCF Reference Manual.
ACS Object
The ACS object represents an ACS subsystem configured for a single physical system. The object
is used to query and control the configuration of the subsystem. The ACS object names are in the
format:
[ system-name. ] $ZACS
where:
is the physical, Guardian name of the system.system-name
You can omit the ACS object name if you have previously used the ASSUME command to assume
it.
64 SCF Command Reference for the ACS Subsystem