Brian, I'm not familiar with TCP/IP for VM - only TCP/IP for MVS in days past. However it appears you could have tried
192.168.2.0/23 192.168.50.1 ETH1 8192 Did you and, if so, did you unearth the same apparent bug? Incidentally I know at least one very helpful TCP/IP developer hangs out in IBMTCP-L if you don't get the definitive answer here. Chris Mason Brian Nielsen wrote: > I've installed z/VM 5.2 and I have this in my GATEWAY statement, and it > works fine: > > 192.168.2.0/24 192.168.50.1 ETH1 8192 > 192.168.3.0/24 192.168.50.1 ETH1 8192 > > This format also works fine: > > 192.168.2.0 255.255.255.0 192.168.50.1 ETH1 8192 > 192.168.3.0 255.255.255.0 192.168.50.1 ETH1 8192 > > > As an excercise, I thought I could supernet these 2 into 1 like this: > > 192.168.2.0 255.255.254.0 192.168.50.1 ETH1 8192 > > but when I do I get the following error message: > > DTCPAR123I Line 75: Unknown link name in GATEWAY cmd > > The message manual says "The message is self-explanatory" and that I > should "correct the problem" and "assist the operator". :-) > > The link name is "ETH1" in all cases, and "ETH1" is used on other route > statements prior to this one. > > I looked for, but didn't find, any TCPIP parameters that might need to be > turned on related to CIDR. > > What am I overlooking? > > Brian Nielsen
