THE FRU summary report provides a summary of error codes logged
and is listed by CUA. THE FRU codes can provide an entry into the
maintenance information (MI) manual for both drive and control unit
failures.
Figure 1 shows an example of the 3490 FRU summary report.
Figure 1. 3490 FRU Summary Report Example3490 FRU SUMMARY 1 REPORT DATE 063 97
PERIOD FROM 049 97
TO 052 97
DEVICE TYPE 3490
3 13
2 C C P 4 5 6 7 8 9 10 11
DEVNO P H C T **** FRU CODE **** **** DATE/TIME ****
/CUA U A U H CU-1 F CU-2 CU-L CUHW DR-1 F DR-2 OCCURRENCES **** LAST ENTRY ****
5A2 E B 0 0 7401 00 7407 7401 D002 0000 00 0000 00001 051/97 19:22:13:31
5A3 E B 0 1 7151 00 7607 CCBB D708 0000 00 0000 00001 051/97 19:03:22:23
5A4 F B 0 1 8E06 0C 0000 0000 0000 192C 00 0000 00001 051/97 21:45:32:21
5A5 F B 1 0 7407 00 7401 7407 D007 0000 00 0000 00001 051/97 20:31:22:45
5A7 F B 0 0 A130 00 3300 0000 D5C1 0000 00 0000 00001 051/97 04:06:33:44
5A7 E B 0 0 7161 00 7161 7161 0000 0000 00 0000 00001 051/97 22:16:37:22
5A7 E B 0 1 7161 00 7161 7161 0000 0000 00 0000 00001 051/97 22:16:18:54
5A7 F B 0 0 3300 40 0000 0000 0000 0000 00 0000 00001 051/97 22:18:38:52
5A7 F B 0 0 7161 00 7161 7161 0000 0000 00 0000 00001 051/97 22:18:40:60
CPU MODEL SERIAL NUMBER 14
E 3081 210819
F 3081 010819
- 1
- REPORT DATE, PERIOD FROM, PERIOD TO
REPORT
DATE is the Julian date the report ran.
PERIOD FROM is the
Julian date of the earliest record.
PERIOD TO is the Julian
date of the latest record.
- 2
- DEVNO/CUA is the device number in XA mode
or the primary control unit address (PCUA).
- 3
- CPU identifies the host processor reporting
the exception and is shown as a value of A through H. The actual
CPU model and serial number are shown at the bottom of the report. CHA identifies the channel adapter that was in use
at the time of error. CU identifies the control
unit containing the channel adapter. PTH identifies
the control unit containing the buffer and data flow in use at the
time of error.
- 4
- CU-ERR1 is the microcode-detected error
code for the first error (control unit or drive), from the OBR record
(sense bytes 10 and 11). This error code should not be used as an
entry to the maintenance package unless efforts using CU-HW 8 and/or
DR-ERR1 9 have not corrected the subsystem problem.
- 5
- CU-F is a microcode-developed flag byte,
from the OBR record (sense byte 9). This byte provides additional
information, if available, for CU-ERR1 4 .
- 6
- CU-ERR2 is the microcode-detected error
code for the second error (control unit or drive), from the OBR record
(sense bytes 12 and 13). This error code can be a result of the first
error indicated in CU-HW 8 , DR-ERR1 9 or
CU-ERR1 4 .
- 7
- CU-ERRL is the microcode-detected error
FRU code for the last error (control unit or drive), from the OBR
record (sense bytes 14 and 15). This error code can be a result of
the first error indicated in CU-HW 8 , DR-ERR1 9 ,
CU-ERR1 4 , DR-ERR2 11 , or CU-ERR2 6 .
- 8
- CU-HW is the control unit hardware-detected
error code from the OBR record (sense bytes 16 and 17). This error
code defines a control unit failure and should be used to enter the
maintenance package if you have multiple drive failures.
- 9
- DR-ERR1 is the drive hardware-detected
error code, from the OBR record (sense bytes 20 and 21). This error
code defines the first failure for any drive and should be used to
enter the maintenance package if you have single drive failures.
- 11
- DR-ERR2 is the drive hardware-detected
error code, from the OBR record (sense bytes 22 and 23). This error
code defines the second or last failure for any drive and should not
be used to enter the maintenance package if you have single drive
failures. This error information provides supplemental information
and can be a result of the first failure (DR-ERR1) in the drive.
- 12
- OCCURRENCES is the total number of times
this error code occurs.
- 13
- DATE/TIME is the Julian date and time
of the last occurrence.
- 14
- CPU, MODEL, SERIAL NUMBER further identifies
the CPU listed in the FRU SUMMARY REPORT.