ASAP 3.0 Messages Manual

HP NonStop Messages Manual Page 89 of 407
Recovery. Manually remove the domain using the ASAPX REMOVE command; then
reregister the domain with ASAPX, or stop the process using the slot and restart the
domain.
1817
Terminated COMMIT, excessive errors: error^cnt
Cause. ASAPX terminated its commit operation because of excessive errors
Error^cnt trying to read the Objectives table. To determine the cause of this event,
see the accompanying file-system error message.
Effect. ASAPX cannot reload objectives for all domains. It terminates the COMMIT
operation to avoid event flooding.
Recovery. Correct the file-system errors and retry the operation.
1818
Command invalid in: fname, Line: number
Cause. ASAPX detected an invalid command line at line number in the configuration
file fname used to start ASAPX.
Effect. ASAPXSGP stops after writing this event message. The ASAPX subsystem is
not started
Recovery. Run ASAPX against the configuration file to determine the invalid
command, correct the command; then restart ASAPX.
1819
DATAITEM not contiguous: fname
Cause. (ASAP Release 1 only) ASAPX detected that the DATAITEM definitions in
fname are not contiguous. There is an error in the ASAPX configuration file.
Effect. ASAPXSGP stops because of the inconsistent configuration. ASAPX is not
started.
Recovery. Redefine the DATAITEMS in fname to use a contiguous sequence of
numbers starting with zero.
1820
DATAITEM definition(s) not defined: fname
Cause. (ASAP Release 1 only) ASAPX did not find DATAITEM definitions in fname.
An error was detected in the ASAPX configuration file.