HP Integrity NonStop H-Series - Manual (Page 83)

Appendix A
WVP Event Analyzer Plug-in User Guide V01 – 536989-001
- 83 -
<Program Name> <Function Name>: Writeupdate Error for file <Filename>:<Error Number>
Relating to function or activity: Updating a key-sequenced file (database file).
Cause: Occurs on the “WRITEUPDATEX” Guardian procedure call. The Guardian error number
indicating what the cause was is part of the event text. Could occur due to various reasons, for e.g. a
record with that key exists already (Error 10).
Effect: If the error occurs on the collector program, the daily database updates or the one-time loads
will not be completed. On the Admin UI functions, the changes made to the admin settings will not
take effect.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 48 can be
recovered from by ensuring proper permissions on the file being written to.
NSEVNTA 119
<Program Name> <Function Name>: Record Not Found in database <Error Detail>
Relating to function or activity: Removing entries from a key-sequenced file (database file).
Cause: Occurs on the “READX” Guardian procedure call when EOF is encountered looking for a
record to remove.
Effect: If the error occurs on the collector program, the daily database updates or the one-time loads
will not be completed. On the Admin functions, the changes made to the admin settings will not take
effect.
Recovery: The error will occur if the EA database being accessed has been tampered with outside of
EA during the course of the operation. Refreshing the EA screen should help in this case.
NSEVNTA 120
EACOLL <Function Name>: $RECEIVE error <Error Number>
Relating to function or activity: EACOLL reading from $RECEIVE for messages from the admin user
interface.
Cause: Occurs on the “READUPDATEX” Guardian procedure call. The Guardian error number
indicating what the cause was is part of the event text.
Effect: The updates made on the Admin screen, relating to change in the daily run time and the trigger
of the one-time loads will not take effect.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 14 (device
non-existent) can be recovered from by ensuring that the processes (for EACOLL and EAVIEW) are
up and running.
NSEVNTA 121
EACOLL <Function Name>: REPLYX Error <Error Number>
Relating to function or activity: EACOLL process replying to a message it receives from the admin
user interface.
Cause: Occurs on the “REPLYX” Guardian procedure call. The Guardian error number indicating what
the cause was is part of the event text.
Effect: The user will not be alerted of the status of the updates made on the Admin screen, relating to
change in the daily run time and the trigger of the one-time loads.