I'm presuming that VM and MVS access this volume at the I/O level. That is, MVS is in another LPAR and is NOT running on VM. If that is not correct, delete this note now. :-S
> So...at this point in time... > is there anything I can do to recover this situation and be able to access > the CDL / Linux files > from the MVS side???? Yes, but it would be a messy DDR hack. IFF you have a spare volume, then perhaps you could DDR from what-Linux-sees to that other volume and then be able to see the content from MVS too. But you'd have to pull a couple of VM tricks too: take the current volume (holding the one enormous minidisk) off-line and bring the new volume (recipient of the DDR transfer) on-line. Not hard, but yet another wrinkle, and you said you're a VM newbe. > And..are you saying that if I formatted the MDISK volume (as defined > below)... using CPVOL FORMAT > then MVS would have been able to successfully access this MDISK ?? > > MDISK 151 3390 0001 3338 LXAD41 MR For what you want to accomplish, the statement should read MDISK 151 3390 0000 3338 LXAD41 MR But as it is, while VM and MVS can both see "LXAD41" there's no guarantee that that is what Linux sees, and if that *is* the label Linux sees, it is because the one-off minidisk coincidentally has the same label. Linux explicitly DOES NOT see the same "volume" that VM sees. You defined the "minidisk" to start at cylinder one. Therefore what Linux thinks is cylinder zero is physically cyl 1. Linux, looking in cyl zero for "LXAD41" does not see the same stuff as VM and MVS see. > If so...is it too late now? Again, with DDR, no. But to recover things using DDR, you *must* use another pack. You can NOT recover this with DDR to the same pack. Strictly speaking, if you think about how the copy would go, it might work. But I would not risk it. "Dangerous, Will Robinson!" -- RMT
