210 Reports
553-3001-358/555-4001-135 Standard 02.00 July 2006
The Maintenance (Error) Report appears in the table in this window.
The window shows the same text lines as those generated by the CLI
SMaint/MReport command.
If the report does not fit on one window, click on the Next Page button
to display more information.
For more information about how the ICB handles error reporting, see
“Error message handling” on page 183.
CLI Maintenance (Error) Report
The Maintenance Report Browser menu enables maintenance reports
to be displayed according to date. These reports analyze system
problems based on error messages compiled on that date. To access
the Maintenance Report Browser menu, login as the administrator.
Enter the System Maintenance command (sm, SM, or SMaint) and
enter the Maintenance Report Browser command (mr, MR, or
MReport).
All reports are time stamped and contain information about the cause
of the problem. After the system displays the data, it returns to the
“year-month-day” prompt using the last selected date as default.
The selected date must be in the past. The system discards old files
that exceed the report aging number of days. If the date entered is too
old, an error message appears. If the date is within the correct date
range, but there are no report entries for that day, a message indicating
there are no messages appears. To interrupt the report display, enter *
and press the Enter key.
The maintenance reports have the following format:
<serial number>: <MON_REPORT_ID> <channel #> <time>
<Applic_Manager_cycle> <Message Body>
Maintenance Report (Error) CLI example
The following example displays the maintenance report for March 15,
1996:
STest, MReport, SCon, ARchivdb, REstordb, CRestart, ?: mr
year(1996): 1996
month (11): 03
day (22): 15
1234:timer101 ch01 16:16:18:111 9000 “Num: 100 Timing Stop. 00.”
1235: sig100 ch00 16:17:05:234 9900 “SIG: Q_APP in msg:0000005A”
0001:HW PCMCIA001 ln0077 ch01 16:25:29:836 PCMCIA card
inserted in socket 1
year (1996): .
STest, MReport, SCon, ARchivdb, REstordb, CRestart, ?: