The Error Log [ Managing HP X.400 Administrator's Guide ] MPE/iX 5.0 Documentation
Managing HP X.400 Administrator's Guide
The Error Log
HP X.400 logs errors to a binary file which contains a set of error and
trace buffers. There are two types of entries in this file, Error and
Trace entries.
Error Entries
An Error Entry records an exceptional condition which occurred in one of
the modules or submodules of HP X.400. Each Error Entry contains:
* the Process ID (PID)
of the logging process,
* a time stamp
* a set of messages resulting from some error or set of errors
called an error history.
The process ID identifies a particular process when such processes exist.
The date and time stamp is useful for filtering out older messages and
for general information.
When an error occurs, the error condition is bubbled up through procedure
and function calls to the top procedure or function where it is logged.
Each procedure and function, which detects an error from a called
function, can add information to the error history.
A single Error Entry often has many error messages within it. These
messages describe the same error event from different software functions
and procedures detecting the error.
Trace Entries
If procedure tracing is enabled, the error log
contains trace entries. These trace entries are a series of function
call entry and exit points. They are used by HP for tracking the
function call flow within a component, and can be used for debugging and
performance analysis. It is useful only if you understand the internals
of the software (e.g. function names within the code). Do not enable
procedure tracing unless you are requested to do so by an HP
representative.
MPE/iX 5.0 Documentation