On Saturday, 01/13/2007 at 03:56 CST, Tom Duerbusch <[EMAIL PROTECTED]> wrote: > I'm in the mist of converting from z/VM 5.1 to z/VM 5.2 and having an IP > problem.
> Actually, I couldn't just take my ZVMV5R10 TCPIP statements and put > them on the newer system. I had to rewrite many of them. Eh? Other than a nag message that your profile is in the old format, everything should have worked, subject to any tighter enforcement of general network design priniciples in the 5.2 stack. > HOME > > 205.235.227.74 255.255.255.000 QDIO1 > > ; (End HOME Address information) > With the VM startup, I got the same errors I've normally had. Of > course, they may be more serious now. > > 15:03:21 DTCPAR123I LINE 231: NO IPV4 HOME ADDRESS FOR DEVICE NEWESA4 > 15:03:21 DTCPDO069I ADDBSDINFO: NO IPV4 HOME ADDRESS FOR LINK LNEWESA4 > 15:03:21 DTCPAR106I DEVICE:NEWESA4, TYPE:CTC > 15:03:21 DTCPAR107I LINK: LNEWESA4, TYPE: CTC, NETWORK NUMBER: 0 > 15:03:21 DTCPDO076I 192.168.99.24 <DIRECT> LINK NAME: LNEWESA4 I infer from those messages and your PROFILE that you are missing the HOME address for NEWESA4. Make sure it is in the VSE subnet, not the OSA subnet. It is required that each link have a unique IP address. An ifconfig -a will likely show the device as "down". Alan Altmark z/VM Development IBM Endicott
