FDRERASE sample outputs

SIMERASE Sample Output

The SIMERASE examines volumes in the range specified (07C0-07CF). SIMERASE identifies those that will be bypassed because they are online and those that are offline and will be erased. SIMERASE also identifies those that have previously been erased by FDRERASE; since ALREADYERASED=PROCESS was specified, the OVERRIDDEN indicates that they will be re-erased. One DASD contained data sets and the default of CHECKTARGET=YES causes it to be bypassed.

The following samples were generated on a test system, erasing a 3390-3 DASD volume in an IBM 2105-F20 Shark on FICON channels. The elapsed times are representative, but your elapsed times may vary depending on your system configuration, type of subsystem, and the number of concurrent erases you execute. By default, one FDRERASE step processes up to 64 DASD volumes concurrently, which may elongate the times of individual DASD but reduces the total elapsed time for all DASD specified.

ERASE Sample Output

The ERASE of a 3390-3 volume took 2.2 minutes, overwriting each track one time. The defaults of one pass with a data record of all zeros were used.

SECUREERASE Sample Output

The SECUREERASE of a 3390-3 volume took 7.1 minutes, overwriting each track three times. The FDR172 messages show the three passes and the data pattern used for each one. Because of the three passes, the DASD TRACKS ERASED in the FDR122 message is three times the number of tracks on the volume.

FDRSUMM Sample Output

If any FDRERASE step (except for a SIMERASE) includes an FDRSUMM DD statement, this contains a 1-line summary of every DASD processed. The title line shows the type of FDRERASE function executed, in this example, it was an ERASE. The erase pattern(s) used or found by verification is shown on the right. If this was for a VERIFY function, the “TRACKS VERIFIED” column shows the number of tracks that were read for verification, even if they did not pass erase verification.

VERIFY Sample Output

This example shows the result of a successful VERIFY of a previously erased 3390-9 DASD. All tracks on the volume were verified.

PRINT Sample Output

This example shows is the result of an FDRERASE PRINT on two tracks of a volume before any data was erased. You can see many data records on each track. There is one line for every record on the track (including Record 0 (R0)). The first and last eight bytes of each record are printed in hex and the first eight bytes are printed in EBCDIC.

This example shows the same FDRERASE PRINT after the volume was erased with ERASE. You can see that each track contains a single track-length (56664 bytes) record containing all zeros (the default pattern for ERASE). “ALL BYTES THE SAME” indicates that every byte in the data record is identical.