So are your OSA devices and Hipersocket devices all on the same network?
 In other words do they all have a 172.20.1.x address with a netmask of
255.255.255.0?

Kim Goldenberg wrote:
We are starting our Linux POC and all has been going well. Until I got
to the Hipersockets, that is.

We are trying to talk to two z/OS LPARs, one development and one
production. in our IFL
LPAR, z/VM 5.2 RSU 0701 and SLES9x SP3. POC is a Java app that gets
messages via
MQ Series and reformats into XML and queries a site on the web via https.

The initial test worked well with MQ talking over the OSAs out to our
internal network and
back in the other OSA (why don't we share them? Don't ask!). Now we want
to modify that
use a Hipersocket interface.

Initial:

z/OS -- OSA -- network -- OSA -- Linux (on vswitch)

Wanted:

z/OS -- Hipersockets -- Linux

Hipersockets were defined on CHPID 50 (addresses 5000-500F) .

xxx.yyy.zzz are the same for all the following addresses:

Both z/OS systems are v1.6.  and have addresses xxx,yyy,zzz,101 and
xxx,yyy,zzz,102
(development and production, respectively) using addresses 500-5002. The
z/OS
systems can ping each other. I set up the z/VM guest to use 5004-5006
through
dedicate statements in the SYSTEM CONFIG and used yast to add configure
the interface
as xxx.yyy.zzz,103. All indications are that the interface is fine:

q osa
OSA  2130 ATTACHED TO DTCVSW2  2130 DEVTYPE OSA         CHPID F3 OSD
OSA  2131 ATTACHED TO DTCVSW2  2131 DEVTYPE OSA         CHPID F3 OSD
OSA  2132 ATTACHED TO DTCVSW2  2132 DEVTYPE OSA         CHPID F3 OSD
OSA  5004 ATTACHED TO LINUX001 5000 DEVTYPE HIPER       CHPID 50 IQD
OSA  5005 ATTACHED TO LINUX001 5001 DEVTYPE HIPER       CHPID 50 IQD
OSA  5006 ATTACHED TO LINUX001 5002 DEVTYPE HIPER       CHPID 50 IQD

lnxa0001:/home/otsgold # ifconfig hsi0
hsi0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
         inet addr:172.20.1.103  Bcast:172.20.1.255  Mask:255.255.255.0
         inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
         UP BROADCAST RUNNING NOARP MULTICAST  MTU:8192  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 b)  TX bytes:1048 (1.0 Kb)

SLES9x info:

lnxa0001:/home/otsgold # uname -a
Linux lnxa0001 2.6.5-7.244-s390x #1 SMP Mon Dec 12 18:32:25 UTC 2005
s390x s390x s390x GNU/Linux

Any ideas as to why the SLES9x will not talk to z/OS? Any thing I should
look for, ask or z/OS network people, etc.?

Kim

--
Kim Goldenberg
Systems Programmer I
State of NJ - OIT
609-777-3722
[EMAIL PROTECTED]
[EMAIL PROTECTED]

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390


--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service:  360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com/in/richsmrcina

Catch the WAVV!  http://www.wavv.org
WAVV 2008 - Chattanooga - April 18-22, 2008

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to