rom: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of
Jeff Gribbin, EDS
Sent: Tuesday, June 27, 2006 12:46 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Volume with minidisks has no allocation information
Further to the comments regarding sharing of DASD between CMS
Further to the comments regarding sharing of DASD between CMS users and
OS - this was routine behaviour at a former employer of mine (back when
DASD was always in short supply). We would format the DASD on the OS side
,
allocate a dataset covering the back end - and then zap the VTOC to flag
I remember hearing about a site that had ALL of its VM volumes available to its
MVS system and had MVS datasets for every minidisk defined. They had all of the
CP areas listed as minidisks too (Checkpoint, Directory, Page, Spool, etc). I
think they did FDR backups and were able to restore full mini
Works fine, for now.
Just overlaying minidisks (or a minidisk over a full pack minidisk),
will work just fine, until the other side tried to write on it. In this
case, if you do a CMS Format, your MVS file will be wiped out. If the
mdisk doesn't overlay the MVS VTOC, MVS will still report the fi
Only slightly off topic, but long ago, just to see what would happen, we
allocated an MVS dataset, and then mapped a CMS minidisk over the dataset's
allocation, and everyone was still happy and running.
As long as everyone agrees to what's been done, there shouldn't be any fussing.
--
Robert
Tom Cluster wrote:
Hello, VM experts,
I'm preparing myself for teaching the mysteries of VSE and VM systems
work and I'm reminded that when one prepares to teach something one
discovers many holes and uncertainties in one's own knowledge. Today
I thought I'd educate myself about IPL bootstr
