Thanks for the responses.  I think I'm hitting up against an MTU sizing
issue.  When set up, the Hipersockers were used between z/OS systems and
were set to have MTU size of 16384.  That worked fine with z/OS.  I seem
to be hitting a wall on z/VM with a max of 8192.  I read about the
LARGEEENVELOPEPOOLSIZE statement, but can not seem to find the right
place to code it in my TCPIP profile to set it above 8192 for my link.  

I'll work on getting a hipersocket defined for an 8192 MTU size.  


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Thursday, March 06, 2008 2:11 PM
To: [email protected]
Subject: Re: z/VM 5.2 Hipersocket Connection to z/OS

On Thursday, 03/06/2008 at 01:04 EST, "Kreiter, Chuck" 
<[EMAIL PROTECTED]> wrote:
> Does anyone have a working TCPIP configuration file for z/VM that 
includes both 
> an ethernet and zSeries hipersocket configuration they would be
willing 
to 
> share?  From z/VM, I can ping both the network and hipersocket address

but I 
> cannot ping z/OS.  Same goes from the z/OS side.  I can ping z/OS to 
z/OS so I 
> think my z/OS hipersocket config is correct. 

You have a routing error.  You didn't post a picture, but it sounds like

OSA ---- z/VM -----HiperSocket----z/OS
       A.1   A.2        |B.1    C.1
                      z/OS
 

1.  You can ping A.1 and A.2 while logged on to A. No surprise.  No 
routing is required.
2.  You cannot ping B.1 or C.1 from A
3.  B.1 and C.1 can ping each other.

Ergo, you have a routing error in either A or (both) B and C.  Check
your 
subnet masks.  Remember that the HiperSocket is a separate subnet.

Alan Altmark
z/VM Development
IBM Endicott

Reply via email to