On Saturday, 04/14/2007 at 07:35 EST, Alain Benveniste <[EMAIL PROTECTED]> wrote: > Our MVS lpar in prod is configured like this : > > PROFILE TCPIP : > DEVICE OSA05P MPCIPA NONROUTER > LINK SVZ1L5 IPAQGNET OSA05P > > MVS has 3 OSA devices. > > Our VM for D/R is configured like this : > > PROFILE TCPIP : > DEVICE OSA82P OSD A200 > LINK OSA82L QDIOETHERNET OSA82P > > VM has 3 OSA devices > > Everything works well. > > The goal is to be able to connect to our MVS in IP in D/R when it is a guest > of the VM above. > > Here are the questions : > > - Are we obliged to have 3 CTC devices known in MVS to be able to code > DEVICE & LINK as CTC in the VM profile tcpip ? > - Can?t we use the 3 OSA devices known in prod ? > - What should be changed in the MVS IP profile ? > - I saw we can code a SPECIAL xxx QDIO in directories. Is it what we have to > use ?
I don't understand. What purpose does the CTC provide? If VM and MVS have OSAs, they are both connected to the network. If MVS is a guest, just attach 3 OSA subchannels to the MVS guest at the address MVS wants them (from the OSA05P TRLE entry). No changes to the MVS IP config are required. If you want to use a VSWITCH rather than dedicated OSA subchannels for MVS, use NICDEF (not SPECIAL, please) to define virtual OSA adapters and couple them a previously-defined VSWITCH. Do not try to connect MVS to a Guest LAN - this will entail reconfiguring MVS. You don't mention your configuration limitations at the DR site, so I assumed that (a) it's z/VM 5.2 and (b) a VSWITCH is suitable. Alan Altmark z/VM Development IBM Endicott
