That's what I though, and sure enough when I DASDFMT the reserved minidisk
the CMS reserve information disappears and the disk can no longer be
accessed "as a file" under CMS.
All dasd ("raw" dasd and CMS RESERVEd minidisks) are handled by the dasd
driver under Linux, right? So device 150 can be raw dasd, dasdfmt'd as
dasda1 and 151 can be a CMS RESERVEd minidisk with an ext2 filesystem as
dasdb1 - we don't use "mnd" anymore, right?
-Thanks folks.
Michael Coffin, VM Systems Programmer
Internal Revenue Service - Room�6030
1111 Constitution Avenue, N.W.
Washington, D.C.� 20224
Voice: (202)�927-4188�� FAX:� (202) 622-6726
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Alan Altmark [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 14, 2002 4:50 PM
To: [EMAIL PROTECTED]
Subject: Re: CMS RESERVED Minidisks
On Monday, 01/14/2002 at 04:31 EST, Michael Short/Towers Perrin
<[EMAIL PROTECTED]> wrote:
> You still need the DASDFMT. The RESERVE only kept the whole disk for
LINUX
> to use; still a CMS function only.
DASDFMT destroys everything done by CMS FORMAT and RESERVE. Only mke2fs
should be required as long as the device drivers still understand
CMS-formatted disks.
Regards,
Alan
IBM Senior Software Engineer
z/VM Development, Endicott, NY
Phone 607.752.6027 fax 607.752.1497 t/l 852
