The tape forced log report and the permanent error summary report
summarize the temporary error OBR records. Look for clusters of errors
that occur within a string of drives or at specific times. This could
indicate a control unit problem.
The Forced Error Log report is generated only when the forced error
logging bit has been set.
Both types of reports have the same format. The only difference
is the heading, one titled Permanent Error Summary and the other Forced
Error Log. Sense byte 7 will be 19 to indicate format 19 sense (temporary
errors) on the Forced Error Log report or 20 to indicate format 20
sense (permanent errors) on the Permanent Error Summary report.
Only the 3422, 3430, 3480, and 3490 devices produce this report.
The errors are listed by channel unit address (CUA) for hardware
errors and by volume identifier (VOLID) for suspected volume errors.
The errors are listed by the CUA unless they occur on the same VOLID
on at least two different drive addresses, then they are listed by
VOLID.
Figure 1 shows an example of the tape
forced error log/permanent error summary reports.
Figure 1. 3490 Forced Log Report Example3490 FORCED LOG REPORT 1 REPORT DATE 063 97
PERIOD FROM 049 97
TO 052 97
11 13 15
**** HARDWARE **** 8 18 10 12 14
16
2 4 6 17 1 1 1 1 1 2
2 2 2 2 3
3 C 5 7 R 9 SENSE BYTES--> 0 2 4 6 8 0 2 4 6 8 0
2 4 6 8 0
CHP DEVNO P TIME W CCW SCSW64-95 -------CU---------- ---DR---- CU
-ID /CUA U DTE HHMMSS VOLID E CMD FLG /CSW32-63 ERR1 ERR2 ERRL HW ERR1 ERR2 SER#
22 5A3 E 051 192213 B35790 E 01 64 060079E0 1044 394A 0000 2C20 0000 7151 7607 CCBB D708 0002 0000 0000 F680 0CE1 0813 3319
06 5A4 F 051 214532 O 00 00 26000000 4048 3934 0000 0020 730C 8E06 0000 0000 0000 0002 192C 0000 F680 0CE1 0813 4419
22 5A7 E 051 221637 TAPENO O 02 44 06000050 0049 402E 0000 0020 0000 7161 7161 7161 0000 0002 0000 0000 F680 0CE1 0813 7700
**** VOLUME OR CREATING DRIVE ****
5A5 F 051 190322 L30570 W 01 64 0E007FF8 0A44 7025 0007 3F20 0000 7404 7401 7407 D007 0002 0000 0000 F680 0CE1 0819 5519
5A2 E 051 203122 L27530 W 01 64 06002090 0A44 3025 000C C620 0000 7401 7407 7401 D002 0002 0000 0000 F680 09E1 0813 2219
5B2 F 051 183221 L30570 W 01 64 0E007FF8 0A44 7025 0007 3F20 0000 7405 7405 7407 D012 0002 0000 0000 F680 0CE1 0819 2219
**** OPERATOR OR OPERATIONAL ****
06 5A3 E 051 205124 M11047 O 01 64 0E002B63 4244 783B 0001 BF20 0000 8202 0000 0000 0000 0002 0000 0000 F680 0CE1 0819 3319
CPU MODEL SERIAL NUMBER
E 3081 210819
F 3081 010819
3490E FORCED LOG REPORT
1 1 1 1 1 2 2 2 2 2 3
C R SENSE BYTES---> 0 2 4 6 8 0 2 4 6 8 0 2 4 6 8 0
CHP DEVNO P W CCW SCSW64-95 --------CU--------- ---DR---- CU
-ID /CUA U DTE TIME VOLID E CMD FLG /CSW32-63 FC-1 FC-2 FC-L HWFC FC-1 FC-2 SER#
06 05B3 F 051 192536 B04012 O 01 64 00000000 0244 6048 000F 5619 0000 7401 7401 0000 D002 0002 0000 0000 F680 0CE1 1249 330E
06 05BB F 051 155433 TAPENO O 03 20 00000000 4240 6048 0000 0019 6C00 8E06 0000 0000 0000 0302 0075 0075 F680 0CE1 1249 BB00
19
CPU MODEL SERIAL NUMBER
E 3081 210819
F 3081 010819
- 1
- 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
- CHPID is the channel path ID (used in XA mode).
- 3
- DEVNO/CUA is the device number in XA mode or the primary
control unit address (PCUA).
- 4
- 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.
- 5
- DTE is the Julian date from the OBR record.
- 6
- TIME is the time from the OBR record.
- 7
- VOLID is the volume serial number.
- 8
- R/W/E/O defines the type of check as Read, Write, Equipment
or Other check.
- 9
- CMD is the command code from the channel command word (CCW)
in the OBR record.
- 10
- SENSE BYTES is the sense data from the OBR record.
- 11
- 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 14 or
DR-ERR1 15 or both have not corrected
the subsystem problem.
- 12
- 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 14 , DR-ERR1 15 ,
or CU-ERR1 11 .
- 13
- CU-ERRL is the microcode-detected error 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 14 , DR-ERR1 15 ,
CU-ERR1 11 , DR-ERR2 16 ,
or CU-ERR2 12 .
- 14
- 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.
- 15
- 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.
- 16
- 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 may be a result
of the first failure (DR-ERR1) in the drive.
- 17
- CCW FLG is CCW bits 32 to 39 from the OBR.
- 18
- SCSW/CSW is:
- SCSW64—95 (in XA Mode)
- CSW32—63
These are the SCSW or CSW bits from the OBR record.
- 19
- CPU, MODEL, SERIAL NUMBER provides further information
on the CPU listed 4 in the error summary
lines of the report.
EREP Reference
Copyright IBM Corporation 1990, 2014