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????
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
If so...is it too late now?
Tia
Dave
David Boyes
<dboyes@sinenom To: [EMAIL PROTECTED]
ine.net> cc:
Sent by: Linux Subject: Re: CDL & Minidisk combo not
working - VTOC FREE SPACE ERRORS
on 390 Port
<[EMAIL PROTECTED]
ARIST.EDU>
02/17/2003
04:08 PM
Please respond
to Linux on 390
Port
> I did not format the volume with CPFMT.
> The volume was previously initialized under MVS using ICKDSF...and it had
> and indexed vtoc on it.
That's probably the problem. VM was never taught how to deal with indexed
volumes. If you're sharing disks between OS/390 and VM, you should
initialize them with DSF CPVOL FORMAT on the VM side (to make sure that
OS/390 is told that a) the volume is full and it shouldn't try to allocate
anything there, and b) that it's not a indexed volume).
> I was able to successfully do this with a volume that was DEDICATED to a
> LINUX GUEST..
> but not this MDISK situation.
With dedicated volumes, the Linux system is dealing with real cyl 0, so it
was able to correctly set up the VTOC as a non-indexed volume.
> I'm a VM newbie...so I guess I know I'm doing something wrong here...
> WHAT STEPS DID I MISS or DO WRONG?
Also make sure that the volumes are marked shared in SYSTEM CONFIG, in the
IOCP, and in the OS/390 config.
