Alan, I separated the networks for LCS and hypersockets. This solved the problem and the QDIO link can now be accessed from another virtual machine (not from outside the network). Removing PORTNAME on the QDIO DEVICE statement resulted in a TCP/IP error message and prevented startup of the link. This may be a TCP/IP release issue: we are still on TCP/IP 4.3. (For PWD members it is no longer easy to remain up-to-date since the VM ADCDs were dropped. Not so for z/OS ...)
Thank you for your advice. Best regards, Antoon Vekeman Software Product Research Software Solutions for DB2 http://www.sprdb2.com B-2288 Bouwel Belgium On Sat, 11 Aug 2007 11:36:20 -0700, Alan Altmark wrote: >On Friday, 08/10/2007 at 05:48 EDT, Antoon Vekeman <[EMAIL PROTECTED]> wrote: >> DTCPRS007E Error encountered in reading PROFILE TCPIP *: >> DTCPAR123I Line 67: Gateway not directly accessible in GATEWAY command >> 00057 HOME >> 00058 192.168.0.3 ETH_VM431 >> 00059 192.168.0.10 QDIO1 >> 00060 ; >> 00061 GATEWAY >> 00062 ; Network First Link MTU Subnet S >> 00063 ; Address Hop Name Size Mask V >> 00064 ; >> 00065 192.168.0 = ETH_VM431 1492 0 >> 00066 192.168.0 = QDIO1 1500 255.255.255.0 0 >> 00067 DEFAULTNET 192.168.0.4 ETH_VM431 1492 0 >You have two interfaces defined with the same subnet (192.168.0/24) that >are connected to different networks. It ain't gonna work. The message is >probably because you don't have EQUALCOSTMULTIPATH in the AssortedParms, >and the first GATEWAY entry was replaced by the second one, excluding >ETH_VM431. >You MUST put the Guest LAN and the LCS device in separate networks. Also, >remove the "PORTNAME" specification for the QDIO device. It isn't >required and its presence will, someday in the unforseen future, come back >to bite you. >Alan Altmark >z/VM Development >IBM Endicott
