Works fine, for now. Just overlaying minidisks (or a minidisk over a full pack minidisk), will work just fine, until the other side tried to write on it. In this case, if you do a CMS Format, your MVS file will be wiped out. If the mdisk doesn't overlay the MVS VTOC, MVS will still report the file exists. But when you open the file to read it, there will be a suprise for you.
If you are using an automated tool, such as Dirmaint, (well, it wouldn't let you define overlapping mindisks in the first place), but if you force it, it may do a CMS Format for you. SOL Also, if the MVS volume was a dedicated volume, trying to put a minidisk on it, would do anything. If you try to link to it (or logon if it is defined to a user), you will get a message that the volume wasn't available. No harm, no foul. OTOH, if you map the entire MVS volume and link it to yourself, you can still ACCESS xxx Z, and use CMS utilities to read the datasets. LISTDS Z (EXTENT to see what is out there. Use FILEDEF or DLBL as JCL. And then use CMS programs to read (not write) the data. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 6/26/2006 4:45 PM >>> Only slightly off topic, but long ago, just to see what would happen, we allocated an MVS dataset, and then mapped a CMS minidisk over the dataset's allocation, and everyone was still happy and running. As long as everyone agrees to what's been done, there shouldn't be any fussing. -- Robert P. Nix Mayo Foundation RO-OC-1-13 200 First Street SW 507-284-0844 Rochester, MN 55905 ----- "In theory, theory and practice are the same, but in practice, theory and practice are different."
