DIAGNOSTICS
Using the Logs
30JUL07
8F2919
Page
320 of 326
14
Note in the retrieved data that only 5 “associations” are indicated “down”.
15
A comparison of the up and down logs indicate that the “leonardo” modality continued to
add “associations” without closing down “associations” until the limit of 12 “associations”
was reached. This prevented new “associations” from occurring.
Contents of the Log
Each line of the log documents an “event”. Each “event” has 16 “columns” of information.
Only 4 or 5 of these “columns” are of use to the FE. (These are in “boldface” in the list
below.) The other data is for use by software engineering. To decrease the size of the log,
these “columns” should be removed from the viewed log by the Options function described in
the preceding section. The “columns”, from left to right, include:
1
“Event Type” - This “column” provides the same information in the Level “column”. It
describes the level provided for the “event”. The levels from highest to lowest are:
TRACE (Level 6), DEBUG (5), DIAG (4), INFO (3), WARNING (2), ERROR (1), and
FATAL ERROR (0).
2
“Time”- Provides the time of the “event”, down to 1/100th of a second. The time is of use
for locating “events” in the log.
3
Code - Code for an “event”. Normally an error code.
4
“Text”- This “column” describes the “event”.
5
“App”- The software application in which the “event” occurred. The applications are:
“MIM”, “DV6800”, and “Service Platform”.
6
Subsystem
- The software subsystem within the application. These include subsystems
of both the MIM and the 6800 LASER IMAGER, described in the tables below.
Subsystems for the MIM include:
