Beware though: if you solve the problem for the second TPF with DEVNO mindisks, VM will still see duplicate volumes when it is IPLed. Now which one will it select to ATTACH to SYSTEM? Normally the one with the lowest address will be selected. But, ... suppose one low-address volume is for some reason offline or very slow, CP will take the higer one and you have a mix of high and low addresses that is attached to SYSTEM and that your first TPF guest with non-DEVNO minidisks would get....
So, either avoid duplicate volumes, or change both TPF definitions to use DEVNO MDISKs or DEDICATE statements. 2009/2/28, Rob van der Heij <[email protected]>: > > 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 > -- Kris Buelens, IBM Belgium, VM customer support
