TS/MP 2.5 Release Supplement

Recovery. Use the STATUS command to check the current state of the ACS subsystem before issuing
the STOP command again.
00012 zacs^err^acs^alrdy^started
ACS 00012 The ACS subsystem is already started
Cause. A START ACS command was issued while the ACS subsystem was already in the STARTED
state.
Effect. The command fails.
Recovery. This is an informational message only; no corrective action is needed.
00013 zacs^err^acs^alrdy^stopped
ACS 00013 The ACS subsystem is already stopped
Cause. A STOP ACS command was issued while the ACS subsystem was already in the STOPPED
state.
Effect. The command fails.
Recovery. This is an informational message only; no corrective action is needed.
00015 zacs^err^down^version
ACS 00015 The PM and subsystem versions are not compatible
Cause. The version identifier from the ACS product module for the SCF interface (ACSPM) indicates
that the product module is older than the ACS domain coordinator process.
Effect. The command fails.
Recovery. Install the appropriate ACS SCF/SCP product module and issue the command again.
00017 zacs^err^acs^not^started
ACS 00017 ACS not yet started
Cause. The CONTROL ACS command was issued while the ACS subsystem was in the STARTING,
STOPPING, or STOPPED state.
Effect. The command fails.
Recovery. Use the STATUS command to check the current state of the ACS subsystem. Issue the
CONTROL ACS command again when the ACS subsystem is in the STARTED state.
00018 ACS object does not exist
ACS 00018 ACS object does not exist
Cause. The ACS object specified in the command does not exist.
Effect. The command fails.
Recovery. Issue the command again and specify a valid object name.
00019 zacs^err^api^error
ACS 00019 API Internal error
Cause. An unexpected Guardian procedure call error occurred within the product module.
SCF Error Messages 87