Hi all, We did a survey at SHARE that you might find interesting. Here are three references relating to Erase on Scratch. Frank and I STRONGLY recommend exploiting it to improve security on the mainframe:
http://watsonwalker.com/cheryls-list-183/ - Blog post recommending EoS http://watsonwalker.com/cheryls-list-188/ - Blog post describing enhancement to EoS http://s3-us-west-1.amazonaws.com/watsonwalker/ww/wp-content/uploads/2016/01/28153156/PR150306.pdf - The Cheryl and Frank zRoadshow at SHARE, March 2015 Best regards, Cheryl ===================== Cheryl Watson Watson & Walker, Inc. www.watsonwalker.com -----Original Message----- Date: Fri, 21 Apr 2017 05:14:38 -0500 From: Bill Wilkie <[email protected]> Subject: Erase on Scratch I have been looking into the Erase on Scratch capability to erase all extents of a data set but much of my research indicates that: 1. You must set up the data set names individually. 2. It will not erase &&Temp data set names unless you: a. Make the &&TEMP name a permanent name. b. Map the temp name to a permanent name already being erased. c. SETROPS ERASE(ALL) to erase all deleted data sets, which is very slow. My question is "Is anyone using it" and if so how is it working out? If you are not using it Why not? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
