On Mon, 12 May 2008 10:47:39 -0400, Mark Pace <[EMAIL PROTECTED]> wrote:
>I created a Hipersockets VLAN. >I stopped the interface in TCPIP, detached the real hipersockets, define d a >NIC and coupled it to the VLAN. >I did the same on the z/OS guest, (which required an IPL, the devices we re >still active after stopping the adapter, VTAM?) and now the z/VM on the VLAN >and the z/OS on the VLAN can talk to one another. >So it's either a real hardware issue, doubtful, or some interaction between >z/VM and z/OS. >I haven't found any hits searching IBMLink. With this connection functioning do a Q LAN DETAILS on the hipersocket LA N to double check that the IP address of your z/OS guest is what you expect it to be, and that it's not VLAN tagged differently or a different PORT name than what you're doing with the other stacks on the real hipersocket . Also, from the z/OS guest what, if any, differences show in various display command outputs from when it was connected to the real hipersocket? What about differences in the JES log for the TCPIP stack? As an aside, you could have avoided removing your VM TCPIP's connection t o the real hipersocket by bringing up a second version of it connected to the hipersocket LAN. Another option would have been to connect your VM TCPIP stack to both the real hipersocket and the hipersocket LAN. Brian Nielsen
