We had a storage array that assigned new tracks as written. So when we got the array empty we wrote all the volumes the requisite number of times.
We had a requirement to erase 3 times (down from 10). On Tue, Feb 21, 2012 at 4:30 PM, Paul Gilmartin <[email protected]> wrote: > On Tue, 21 Feb 2012 16:19:53 -0600, Judy Schultz wrote: >> >>Thank you for your reply. If the Unconfigure unformats the disk group >>writing binary zeroes, why do you need to use the TRKFMT ERASEDATA >>CYCLES(1) command first before the Unconfigure? >>T > The debate rages. One side insists that one must overwrite the data many > times before it's really gone. For an opposing view, see: > > > http://www.h-online.com/security/news/item/Secure-deletion-a-single-overwrite-will-do-it-739699.html > > ... which mentions a more realistic concern that there may be residual > data in editor recovery files, page data sets, etc. And with modern > virtual DASD with technologies such as copy-on-write, you have little > assurance that you're overwriting the data you wish to secure. > > -- gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
