If the DASD is accessible by more than one system, perhaps some activity on the other system is the source of the corruption.
Brian Nielsen On Tue, 31 Oct 2006 13:29:48 -0800, Schuh, Richard <[EMAIL PROTECTED]> wrot e: >Neither one is on the system where the corruption occurred. It is so specialized and stable that there is rarely any need to even look at the directory, much less update it. We have access to the disks from our main VM system, so we allocate new M-disks there using VM:Secure and copy the resulting mdisk statements to the small system. > >Regards, >Richard Schuh
