Table of Contents
Advertisement
Tuning, Troubleshooting, Security, and Maintenance
Troubleshooting: How ITO Reports Errors
be that messages relating to serious or critical problems are marked as
"X" in the "U" (Unmatched) column in the message browser and, as a
consequence, possibly ignored.
In addition, such unmatched messages should be reported to the ITO
administrator, in order to improve the existing templates by adding
appropriate message or suppress conditions.
Errors Reported via the GUI Error Dialog Box
Any errors which relate to the GUI processes are displayed in an error
dialog box, which automatically pops up when required. Typical error
situations are:
User errors:
• syntax errors when typing input
• semantic errors (for example, unknown system)
• required objects not selected while performing a task
Communication problems between user interface processes and the
display manager (for example, an action cannot be performed because
the management server is down). This includes errors reported from
X applications and applications configured as No Window started
from the Application Desktop, and errors reported by starting
operator-initiated actions.
Errors originating from HP OpenView functionality used in the GUI
(for example, a submap can not be created, because the HP OpenView
Windows map does not have write permissions).
Problems in retrieving or writing data to or from the database (for
example, it may not be possible to get detailed message information
from the database).
All these errors are reported in the error log files. If problems with the
database occur, the user receives a general message that a problem
exists, while more detailed information is written to the error log file.
388
Chapter 10
Advertisement
Table of Contents
Troubleshooting
