Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Erasing DASD Data z/OS DFSMS Using Data Sets SC23-6855-00 |
|
When you delete any DASD data set or release part of the space, the system makes the space available for allocation for new data sets. There are ways that the creator of the new data set can read residual data that was in the previous data set. To prevent others from reading your deleted data, run a program that overwrites the data before you delete it. Alternatively, you can have the system erase (overwrite) the data during data set deletion or space release, with its erase-on-scratch function. The system erasure is faster than a program that writes new data. If the system erasure fails, then the deletion or space release fails. The objective of the erase-on-scratch function is to ensure that
none of the data on the released tracks can be read by any host software
even if the device is mis-configured and connected to a different
computer with different software. However, after the erasure, the
old data on those tracks remains exposed to the following risks, which
you must evaluate:
To have the system erase sensitive data with RACF, the system programmer
can start the erase feature with the RACF SETROPTS command. This feature
controls the erasure of DASD space when it is releases. Space release
occurs when you delete a data set or release part of a data set. SETROPTS
selects one of the following methods for erasing the space:
If the ERASE option is set in the RACF profile, you cannot override the option by specifying NOERASE in access methods services commands. |
Copyright IBM Corporation 1990, 2014
|