I'm not sure if this will resolve your entire problem, but you definitely
have an incorrect gateway statement.
Assuming, you want a route to the 10.10.38.64 network, you want the gateway
as follows:
GATEWAY
; Network First Link MTU Subnet Subnet
; Address Hop Name Size Mask Value
; -------- ----------- -------- ----- --------- --------
10 = OSA1 1492 0.255.255.224 0.10.38.64
DEFAULTNET 10.10.38.65 OSA1 1492 0
;
Peggy Williams
607-429-4063
z/VM - TCP/IP Development
Thomas Kern
<[EMAIL PROTECTED]
o.com> To
Sent by: The IBM [email protected]
z/VM Operating cc
System
<[EMAIL PROTECTED] Subject
ARK.EDU> TCPIP GATEWAY definition - 2nd
level stack to 1st level vswitch
02/16/2007 03:02
PM
Please respond to
[EMAIL PROTECTED]
.com
I am trying to get a 2nd level TCPIP stack to properly talk to a 1st
level vswitch. I need to get to this 2nd level stack from the other side
of the vswitch. I have a 1st level vswitch connected to an OSA with
addresses in the range of 10.10.38.64-10.10.38.95 (gateway =
10.10.38.65). I have the vswitch grants in place to authorize my 2nd
level test machine to connect to it and I have a NICDEF statement in the
directory entry. The 2nd level machine ipls, its TCPIP server aquires
the virtual devices for the NICDEF and starts the stack. At this point
the stack will either not communicate with anything or only with systems
that are also on the 1st level vswitch. I have tried variations on the
GATEWAY statements and this is the set that will allow me to communicate
with other vswitch guests but not beyond.
GATEWAY
; Network First Link MTU Subnet Subnet
; Address Hop Name Size Mask Value
; -------- ----------- -------- ----- --------- --------
10 = OSA1 1492 0.0.0.224 0.0.0.64
DEFAULTNET 10.10.38.65 OSA1 1492 0
;
And I get this message when I bring up the stack or use OBEYFILE with
these statements (line number is different in stack initialization).
DTCPAR123I Line 6: Unknown link name in GATEWAY cmd
/Tom Kern
/301-903-2211
