ASAP 3.2 Messages Manual

HP NonStop Messages Manual Page 282 of 414
Effect. The Collector logs the error and continues to process the control file. If the
entire file is corrupt or invalid, the database is created using default settings. If some
entries in the file are good, they are used to create the database.
Recovery. Shut down and restart the Collector to re-create the partition control file.
Data Tokens.
ZEMS-TKN-TEXT contains the message text.
ZASP-TKN-ASAP-ERRORNUM is ―2036‖.
2037: ZASP-EVT-COL-CTL-WRITE-ERROR
Collector could not write partition ctl file error
error
is the file-system error number. If greater than 0, it indicates the encountered file-
system error. If less than 0, it indicates an internal ASAP error.
Cause. The Collector could not write status information to the partition control file after
reading the file. The cause is most likely a security violation.
Effect. The Collector logs the error and continues to run normally. Status information
is not written to the control file, but Collector operations are not otherwise affected.
Recovery. Depends on error. If an internal ASAP error occurred, contact your
support representative.
Data Tokens.
ZEMS-TKN-TEXT contains the message text.
ZASP-TKN-ASAP-ERRORNUM is ―2037‖.
2038: ZASP-EVT-COL-PART-BAD-SUFFIX
Unknown suffix entity-suffix
entity-suffix
is the suffix for an ASAP entity.
Cause. The Collector encountered an unknown ASAP database entity suffix. The
cause is an internal Collector error, possibly due to a versioning inconsistency.
Effect. The Collector does not create a database for the specified entity.
Recovery. Contact your support representative.
Data Tokens.
ZEMS-TKN-TEXT contains the message text.