OK, so I took out the statements in the HOME area. When I did that, VSE (via VCTCA, or the sole Linux image that is still using IUCV) wouldn't connect anymore.
On the VSE side (guest machine NEWESA4), I now get the following, no matter what other changes I make to the VM side: 0016: IPL380I Internet Link Level (ILL) Startup CTC Adapter, Cuu:0982 Link: LINK02 0016: IPL395E Senseid I/O error on receive port, Cuu:0982 Sns:41 LinkID: LINK02 0016: IPL391E Unable to Initialize CTC Adapter, Cuu:0982 Linkid: LINK02 Or, from the Linux side (SUSE9 31 bit SP1) guest machine LINUX27 ifconfig iucv0 Link encap:Serial Line IP inet addr:192.168.99.227 P-t-P:205.235.227.74 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MTU:9216 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:30 dropped:30 overruns:0 carrier:30 collisions:0 txqueuelen:50 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >From VM, ifconfig -a shows: QDIO1 inet addr: 205.235.227.74 mask: 255.255.255.0 UP BROADCAST MULTICAST MTU: 1500 vdev: 2110 type: QDIO ETHERNET portname: UNASSIGNED ipv4 router type: PRIMARY ipv6: DISABLED cpu: 0 forwarding: ENABLED RX bytes: 2388103 TX bytes: 38835113 LNEWESA4 inet addr: <NONE> mask: ? DOWN BROADCAST MULTICAST MTU: 9216 vdev: 0922 type: CTC portnumber: 0 connects to: NEWESA4 0983 cpu: 0 forwarding: ENABLED RX bytes: 0 TX bytes: 0 LLINUX27 inet addr: <NONE> mask: ? DOWN BROADCAST MULTICAST MTU: 9216 type: IUCV connects to: LINUX27 cpu: 0 forwarding: ENABLED RX bytes: 0 TX bytes: 0 My latest iteration of my VM IP setup (I spent a lot of time last night, playing with it): HOME 205.235.227.74 255.255.255.000 QDIO1 ; 192.168.099.227 255.255.255.240 LLINUX27 ; 192.168.099.024 255.255.255.240 LNEWESA4 ; 192.168.099.010 255.255.255.240 LY2KESA2 ; (End HOME Address information) ; ---------------------------------------------------------------------- ; ---------------------------------------------------------------------- ; Primary interface Definition ; ---------------------------------------------------------------------- PRIMARYINTERFACE QDIO1 ; ---------------------------------------------------------------------- GATEWAY ; Network Subnet First Link MTU ; Address Mask Hop Name Size ; ------------- --------------- --------------- ---------------- ----- ; 205.235.227 255.255.255.0 = QDIO1 1500 192.168.099.024 255.255.255.240 = LNEWESA4 1500 192.168.099.000 255.255.255.240 = LY2KESA2 1500 192.168.099.227 255.255.255.240 = LLINUX27 1500 DEFAULTNET 205.235.227.41 QDIO1 1500 ; (End GATEWAY Static Routing information) I can't do much with it today, but I have time tonight to make changes. My current plans is to move the last remaining Linux image that is using IUCV to VSWITCH to bypass that problem. As far as the old VSE systems (VSE/ESA 2.3.2 with TCP/IP 1.5B), I might try, instead of using the VM stack as a router, see if I can use a more current VSE that is using Vswitch, and have that VSE be a router for the older VSE systems. But I don't think it is a problem with the VM stack. I really think it is a problem with my knowledge <G>. My attempt at using a mask of 255.255.255.240 would produce an unique network address for each of the 192~~~ hosts. That didn't work either. I get the feeling that I'm working on the wrong part, and the actual problem is somewhere else. Thanks for any insight to this problem. Tom Duerbusch THD Consulting R'uh r'oh....the IP addresses you have in the HOME statement are identical to those in your GATEWAY statement. NG. The entries in the HOME list are the IP addresses assigned to your *VM* system. Those in the GATEWAY are those assigned to the hosts on the other end of the CTCs. You also have overlapping subnets on the HOME statement. A point-to-point connection is more typically a .252 subnet. The overlap isn't fatal since you have HOST entries. Further, get rid of the GATEWAY entry for QDIO1 and put the MTU on the LINK statement. Draw a picture and you will see that you have 4 subnets; one to the OSA and one to each of 3 hosts. Your network config files should implement that configuration with 4 non-overlapping subnets with VM TCP/IP as the router. Alan Altmark z/VM Development IBM Endicott