Before you run off and format the drive again, from the sound of your
description, you either attached the disk to a user and queried it, or you
created a minidisk that covered the drive, including cyl 0. That's about the
only two ways you'd get a message about it being an OS disk.
You need to allocate one or more minidisks on the drive, beginning at cyl 1
and continuing up from there, and format each minidisk as a CMS disk.
Also, how much "stuff" does this person have? 3338 cylinders seems like huge
overkill for a CMS disk. I'd see what he has, and maybe 50 (or maybe 5)
cylinders would be enough. Don't waste the space; you'll find other uses for
it in the long run.
--
.~. Robert P. Nix Mayo Foundation
/V\ RO-OE-5-55 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."
On 10/26/07 9:10 AM, "Anne D. Crabtree" <[EMAIL PROTECTED]> wrote:
> Ah! It was the cms format I was forgetting. Thanks so much.. My brain
> isn't working too well today... tgif
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
> Behalf Of Alan Altmark
> Sent: Friday, October 26, 2007 10:02 AM
> To: [email protected]
> Subject: Re: DASD question
>
> On Friday, 10/26/2007 at 09:39 EDT, "Anne D. Crabtree"
> <[EMAIL PROTECTED]> wrote:
>> I have a mod 3 that is known to VM:
>>
>> DASD 1472 LX1472
>>
>> I want it to be a mdisk on MAINT and have all my linux instances link
> to
> it.
>>
>> I formatted LX1472 with CPFMTXA.
>>
>> It is not in the User_Volume_List but I added it for next ipl.
>>
>> I tried attaching 1472 to SYSTEM, but when I try to access the vdev
> 1472, it
>> says it?s in OS format.
>
> 1. ATTACH 1472 TO MAINT
> 2. Using CPFMTXA, allocate the entire volume as PERM and label the
> volume.
> It is not necessary to *format* the volume unless there is residual
> data
> on it that you wish to erase OR you are going to use it to contain CP
> data
> (spool, paging, parm, ...). Remember that the guest will turn around
> and
> format it for its own use (whether Linux or CMS) and there's no point in
>
> formatting the volume twice! (And, no, cylinder 0 does not have to be
> formatted unless you mark cylinder 0 as PAGE or SPOOL.)
> 3. Update your directory (e.g. $ALLOC$) cylinder 0 of that volume is in
> use and/or update your directory management product configuration files.
> 4. Update SYSTEM CONFIG
> 5. DETACH 1472 MAINT
> 6. ATTACH 1472 TO SYSTEM
> 7. Allocate minidisks on it.
> 8. The guest that owns the minidisk can format it.
>
> Alan Altmark
> z/VM Development
> IBM Endicott
