Rob -- Worked perfectly, at least after I had taken the subject volumes out of the include list.
Many thanks, i ------ Original Message ------ Received: Sat, 28 Feb 2009 03:28:41 PM COT From: Rob van der Heij <[email protected]> To: [email protected] Subject: Re: Dasd with duplicate volids > On Sat, Feb 28, 2009 at 8:41 PM, Ian S. Worthington > <[email protected]> wrote: > > I have an ipl-able system (tpf) running under vm that I need to duplicate. > > The tpf generation defines which volids the system will look for, but, iiuc, > > vm won't attach dasd with duplicate volids. > > > > What's the best way of handling this? Is there any capability to attach that > > dasd with duplicate volids to the correct virtual machines? Or is there any > > capability to attach dasd volumes to a virtual machine and change the volid as > > seem from that machine? > > > > Look at the DEVNO option of the MDISK statement in the directory. That > lets you use the device address. If you think you don't need VM MDC > for them, you could just dedicate them (and have the (dup) volser not > attached to SYSTEM). > > If you want to be completely isolated, you should start the mini disks > at cylinder 1 so CP is free to use volsers that work for the entire > installation, where TPF can have its own (virtual) volser. But you may > not be in a position anymore to pick that approach. > > Rob >
