DASD Data Transfer Summary

This report further explains the data checks listed in the DASD subsystem exception report.

The DASD data transfer summary lists:

Each volume that experienced data checks, giving the error locations for each
Cylinder and head error locations
Probable failing unit (PFU)
Other information which helps narrow down the cause of errors

It can be in two parts:

PFU of volume
PFU of other than volume

Since the report is sequenced by PFU, it is helpful for looking up failures categorized by PFU.

All data checks listed on the system error summary part 2 and the DASD subsystem exception report will be listed under the PFU—Volume part of this report.

If volume is specified as the PFU, the customer should try to correct the problem using a utility program such as the device support facility. This will correct the errors by:

Rewriting the data
Generating a skip displacement
Assigning an alternate track
Indicating a bad drive

The IBM service representative should correct errors listed as Other by using the report information and the maintenance package. These errors have a very high probability of being caused by hardware.

Compare later reports to ensure that failing addresses no longer appear in the reports.

The DASD string summary can be used to verify that a drive is also being used.

DASD Data Transfer Summary—PFU-Volume shows the PFU by Volume. The report may also show the PFU by Other.

DASD Data Transfer Summary—PFU-Volume

DASD DATA TRANSFER SUMMARY                          REPORT DATE 175 97
PROBABLE FAILING UNIT - VOLUME                      PERIOD FROM 041 97
                                                           TO   059 97

                                                             SENSE COUNTS  1 
                                                               TEMPORARY
                                                              OFFSET INVK THRESHOLD
                                                         PERM   NO   YES   LOGGING
***********************************************************************************
SEQUENCE BY VOLUME LABEL, HEAD, CYLINDER
    2 
UNITADDRESS 0380   DEVTYPE 3310         VOLUME DOSAF3   5 
      3 
     CPU 26   PHYSICAL ADDRESS 0590   4 
     FAILURE AT BLOCK: 3834      CCHS 0010-09-26            0     1     0     0
   08015000 0A091A50 06000012 0000004D 004D01C4 28000000   6 
                     LAST SENSE AT: 045⁄97  07:52:15:81

UNITADDRESS 06C7   DEVTYPE 3330         VOLUME TSO190
     CPU 27   PHYSICAL ADDRESS 06C5

     FAILURE AT ADDRESS: CYLINDER 0158  HEAD 01             1     0     0     0
   08800000 159E0143 009E0001 0A1F301B 60000000 00004943
                     LAST SENSE AT: 044⁄97  10:43:02:62


UNITADDRESS 0921   DEVTYPE 3350         VOLUME DSAPAK
     CPU 35   PHYSICAL ADDRESS 0921
            7 
     FAILURE AT ADDRESS: CYLINDER 0385  HEAD 26             0     1     0     0
   00001000 40813A40 0181801A 00000000 00000000 00004940
                     LAST SENSE AT: 050⁄97  16:18:38:16


UNITADDRESS 0381   DEVTYPE 3370         VOLUME DOSAF3
     CPU 30   PHYSICAL ADDRESS 0380

     FAILURE AT BLOCK: 3413      CCHS 0004-05-49            0     0     0     1
   08015000 04053150 06000006 00000059 00590093 06000000
                     LAST SENSE AT: 045⁄97  07:52:05:07

UNITADDRESS 0734   DEVTYPE 3380         VOLUME PAK167
     CPU 07   PHYSICAL ADDRESS XX-84-04

     FAILURE AT BLOCK: CYLINDER 0148  HEAD 07               1     0     0     0
   08800000 84940743 00020007 066C8400 00000000 00314943
                     LAST SENSE AT: 043⁄97  14:25:47:01

UNITADDRESS 0D17   DEVTYPE 3390-01      VOLUME SOQV31
     CPU 0A   PHYSICAL ADDRESS GRAM9.X-17

     FAILURE AT BLOCK: CYLINDER 0025  HEAD 14               0     0     2     0
   18000504 1726CE98 00001E00 08400004 2224CB83 11444320
   00800E01 0000109E LAST SENSE AT: 058⁄97  13:56:55:11
UNITADDRESS 0F50   DEVTYPE 9335         VOLUME DSFF50
     CPU 13   PHYSICAL ADDRESS 0F50

     FAILURE AT BLOCK: 4097      CCHS 0083-01-50            1     0     0     0
   08800000 53013241 00000000 00000000 00000000 10014401
                     LAST SENSE AT: 048⁄97  16:25:17:43

-----------------------------------------------------------------------------------
THE FOLLOWING ENTRIES HAVE ONLY MDR RECORD TYPES. THEREFORE, NO CYLINDER/HEAD   8 
ADDRESSES ARE REPORTED. SEE THE EXCEPTION REPORT FOR THE ERROR COUNTS.

UNITADDRESS 0597   DEVTYPE 3310         VOLUME ERPVOL
     CPU 26   PHYSICAL ADDRESS 0597


NOTE: CYLINDER/HEAD/BLOCK NUMBERS ARE DECIMAL VALUES
NOTE: UNITADDRESS IS THE LOGICAL ADDRESS OF THE DEVICE
NOTE: ? FOLLOWING THE PHYSICAL ADDRESS DENOTES MULTIPLE
      PHYSICAL UNITS HAD ERRORS WITH THIS VOLUME LABEL

1

These columns contain counts of the data checks for the particular cylinder/head or block. The permanent data checks appear in the first column. The temporary data checks are broken down as follows:

COLUMN	DESCRIPTION
`OFFSET INVK` (offset invoked)	Indicates the number of recovered temporary data checks, and whether it was necessary to offset the access mechanism with the `NO` and the `YES` sub-columns
`THRESHOLD LOGGING`	Indicates the number of temporary data checks recorded when the device was in logging mode because the threshold for data checks was exceeded.

2

The keyword used by the device support facility to identify the device. It is the logical address (SCUA) or device number of the volume reporting the error.

3

The CPU identified for the last sense record.

4

For devices providing physical IDs, this is the physical ID; for other devices, it is the PCUA or physical device number.

5

The volume serial number of the volume reporting the error.

6

There may be either 24 or 32 sense bytes in the last sense record received for this cylinder and head or block. The format of the sense record is in byte 7 and is shown in the following table:

FORMAT	DESCRIPTION
4	The symptom code is in the last two sense bytes
5	The value in byte 7 is repeated in the last two sense bytes

The date and time follow the sense bytes.

7

The location of the data check as shown in the following table:

FOR	ADDRESS
Count key data (CKD) devices	The address is expressed as cylinder and head
Fixed block (FBA) devices	The address is expressed as block number
Note: The values are in decimal. When a volume records data checks at more than one location, the report includes an entry for each location and puts them in ascending order.

8

In cases where the only error data is from error counters, meaning that failure addresses are not available, only the lines that define the device and volume appear.