The usage information in the DASD string summary can help you determine whether a failure affect reported in the DASD subsystem exception report is associated with just one device or is common to more than one device in the same controller string.
The report is useful in helping analyze error causes. It is used in conjunction with the DASD subsystem exception report.
DASD STRING SUMMARY (1) REPORT DATE 105 97
PERIOD FROM 100 97
TO 104 97
REPORT INCLUDES ALL DASD WITH PHYSICAL IDS OR A VALID DASDID
ERROR TYPES SEEK MEGABYTES
EQU. ³SEEK ³DATA ACCESSES MEGABYTES WRITTEN
SSID SCU CTLR DEV VOLUME CHKS ³ ³XFER X 1000 READ W/VERIFY
***********************************************************************************************
26 34 1 2
27 35
08 MX1RS1 8 137
09 MX1DL1 66
22 66.0
23 60.1
02
02 RAS7C2 Y Y Y
03 RAS7C3 Y Y Y
07 80
23 80.1
02 RAS7C2 Y
03 RAS7D3 Y
05 IBM355 Y
03 A5
02 RAS712 35 73
03 RAS713 34 80
0C RAS71C 31 68
0E RAS71E 31 77
0F RAS71F 31 69
0004 10114.0 0F.0
10114.2 0F.2
01 RAS841 65 3
05 RAS845 65 3
06 RAS846 65 3
0041 .1 01.1
11 RAS291 Y
0243 .0 00
HHGK6.0 00
ZZZ23-0F SOQV04 131 112
ZZZ23-0F SOQV06 Y
1144 .0 00
DBDMC.0 00
AH210-02 SLT221 2
AH210-02 SOQV01 65 2
95122-14 SOQV19 Y
RM102-16 SOQV09 Y
GRAM9-17 SOQV31 Y
95122-1E SOQV21 Y
*****-1F SOQV13 Y
1144 .0 01
DBDMC.0 01
GRAM9-10 SOQV03 65 287
GRAM9-10 SOQV05 Y
ALL DASD PROCESSED FOR EXCEPTION REPORT 1530 9325 3
***********************************************************************************************
NOTE: THE COUNTS FOR SEEK ACCESSES X 1000, MEGABYTES READ, AND
MEGABYTES WRITTEN W/VERIFY ARE SIX DIGIT POSITIONS. IF THE
SPACE IS EXCEEDED, THE COUNT IS DIVIDED BY 1000 AND A K IS
PLACED AT THE END OF THE NUMBER. IF THE COUNT IS EXCEEDED
WITH A K AT THE END, 99999K WILL BE PRINTED.
FAILURE AFFECT | ERROR TYPE COLUMN WITH A Y |
---|---|
CTLR | EQU.CHKS |
CTLR/DEV | EQU.CHKS |
DEV | EQU.CHKS |
SEEK | SEEK |
DATAXFR | DATAXFER |
DATAXFR(HDA) | DATAXFER |
MULTIPLE | Any combination |