In a message dated 1/22/2007 8:16:41 A.M. Central Standard Time, [EMAIL PROTECTED] writes: >think IBM's answer to the security issue is an erase feature. There is no other way to enforce the requirement that user A's data cannot be read by user B after user A has released ownership of the tracks and user B subsequently is allowed to allocate the same tracks. Just don't start erasing all tracks in all data sets willy-nilly, or you may have DASD performance problems like you wouldn't believe. Be VERY selective about what you erase. Bill Fairchild
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
