On Friday, 05/09/2008 at 02:10 EDT, Mark Pace <[EMAIL PROTECTED]> wrote:
> I need a LAN connected to real Hipersockets to test this problem.
>
> Well maybe not, just to test connectivity I could try just VM's TCPIP
and the
> z/OS guest. If it works, then know I know I have some odd hardware
problem.
Since you didn't draw a picture (whack!), let me do so based on my
observations from your posts. You've got 5 hosts in a single CEC trying
to use HiperSockets:
CHPID FF
10.6.0.0/24
----+---------+------------+----------+----------+
| | | | |
VM TCP#1 MVS LPAR MVS Guest VM TCP#2 VSE Guest
10.6.0.4 10.6.0.3 10.6.0.5 10.6.0.2 ??.??.??.??
MTU 1496 1496 1496 1496 ????
OK so far?
Problem statement: "MVS Guest" cannot communicate with at least one of
the VM TCP/IPs. (I'm not sure which.) You CAN communicate among all
other users of the HiperSocket.
There was a reference to OSAs, but I considered it to be a red herring
since they (the OSAs, not the herring) are not involved in getting data
across a HiperSocket.
Can you clarify what is communicating successfully via HiperSockets and
what isn't?
Just to exlude a rare ailment, for each VM guest (incl. TCPIP),
1. Issue #CP Q V xxxx (where xxxx is the device address of one of the
HIPERS devices)
2. Using the Subchannel = yy value on the output from #1, issue #CP D
SCHIB yy
3. Verify that the virtual chpid number is FF000000 00000000
For VM TCP/IP, you can just NETSTAT CP <command>. No logon required.
Alan Altmark
z/VM Development
IBM Endicott
