On Wednesday, 10/04/2006 at 04:30 AST, "Post, Mark K" <[EMAIL PROTECTED]> wrote: > If you use the DASD driver recently talked about here, yes. (At least > the first volume of it, I don't know about the rest. Perhaps the driver > author could clarify that.) I would certainly not recommend it however. > The auditors are likely to have a fit.
And trying to do this on a live MVS system is unreliable at best. Let MVS read the data since he knows where everything is located. He can even find it if it has been migrated elsewhere. As a general rule, disk snooping makes my skin crawl. 1. It tears huge holes in the security and data integrity fabric of the universe. The victimized operating system cannot audit the fact that you accessed the data and that could violate both company audit policy and governmental regulations. Convenience and performance aren't the best defenses. 2. You risk getting [apparently] corrupted data if the victim decides to update things whilst you're snooping. 3. If you take action to prevent #2, then you risk operational interference. Of course, if the victim or the data doesn't fall under any particular security policy and data integrity isn't all that important, "never mind". I make exceptions for emergency data/system recovery operations, of course. I mean, if you have no alternative, ok, but if alternatives exist, use them. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
