On Thursday, 03/02/2006 at 08:29 CST, Mike Walter <[EMAIL PROTECTED]> wrote:
> Will the new function define the DASD size in the VTOC based on the size of the > real (emulated, sigh) DASD, or the MDISK size that a virtual machine running > ICKDSF sees when the command is issued? This gets back to Jeff's report that > linking to an MDISK defined to map only cylinder zero of the real (emulated) > DASD resulted in a VTOC describing a one-cylinder 3390 (what's that, a model > 3390-.1113?). If you run the new function while linked R/W to just cyl 0, the device will report a size of one cylinder and the VTOC will describe a one-cylinder disk. Then when you use DFSMSdss, it will whine that the VTOC and device dimensions don't match and that it is ignoring the VTOC (as you would want). So if you want to refresh the VTOC, be sure you do it when you have a full-pack mini or when you have volume dedicated. And it is probably worth updating if you're sharing with MVS simply to avoid someone from issuing the REFORMAT REFVTOC from MVS. (All of this upheaval originally because someone didn't like the whining from DSS.) Alan Altmark z/VM Development IBM Endicott
