In a prior life at a bank, we did a DR exercise at a vendor business recovery site. At the end, we were supposed to erase all the data we had restored. We did the RACF needful to erase on delete, started some kind of 'delete all' process, and went out to lunch. Came back a few hours later. It was still running. Those were the days of slow CPUs and slow DASD. We had a plane to catch. Asked the vendor to let it run to completion. Took off.
If you can't trust IBM, who can you trust? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Walt Farrell Sent: Friday, April 21, 2017 5:39 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Erase on Scratch On Fri, 21 Apr 2017 11:12:25 +0000, Vernooij, Kees (ITOPT1) - KLM <kees.verno...@klm.com> wrote: >You don't mention what you want to use it for, but with SMS managed >datasets part of the problem was eliminated, because SMS managed >datasets automatically get an EOF. You can't anymore simply allocate a dataset >and start reading the old data on the tracks. True. However, that only erases the data from the first track of the data set, and anyone using EXCP-level programming can still read the rest of the data. -- Walt ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
