Tim--VM would be quite happy with a full volume, 3339 cyl. mdisk that
the guest would get. Now that does leave you with the exposure of the
VSE guest "owning" cyl 0, including the label. If you change the label,
VM won't know about the different label until you change the MDISK
statement in the directory. There is an option on the MDISK statement
that allows you to define a MDISK at a real address rather that by volid:
MDisk /vdev devtype /DEVNO /rdev /
The message you are seeing is normal.
Jim
Tim Joyce wrote:
This is a multi-part message in MIME format.
------_=_NextPart_001_01C78357.994BD268
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hello,
=20
I am testing procedures to migrate my dedicated VSE volumes to VM full
volume minidisks. I have run into trouble when using DDR to copy my
dedicated 3390 (mod3) pack to the virtual (3390 mod3) volume. I get :
=20
HCPDDR725D SOURCE DASD DEVICE WAS (IS) LARGER THAN OUTPUT DEVICE.
=20
I assume this is because my minidisk is defined a 3338 and the dedicated
pack is 3339 .. is this correct?
=20
I figure many of you have done this is the past and may be able to
suggest the best way to do this.=20
=20
Thanks, Tim
~~~~~~~~~~~~~~~~~~~~~~~~
Tim Joyce
Sr. Systems Programmer=20
Alex Lee, Inc.=20
Email : [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> =20
Phone: (828) 725-4448 =20
Fax: (828) 725-4800
=20
--
Jim Bohnsack
Cornell University
(607) 255-1760
[EMAIL PROTECTED]
