Greetings All!
We have been struggling trying to get our z/VM & z/OS systems to talk via
hipersockets to our RHEL5.3 Linux (under z/VM 6.1). We can ping out from
Linux to VM or to z/OS, but when we ping into Linux from z/VM & z/OS the
'tcpdump -I hsi0 ip proto \\icmp' on th
On 07/20/2010 01:47 PM, Bauer, Bobby (NIH/CIT) [E] wrote:
> ifcfg-his- has:
I suppose it's /etc/sysconfig/network-scripts/ifcfg-hsi0
> DEVICE=hsi0
> BOOTPROTO=static
> ONBOOT=yes
> NETTYPE=qeth
> MTU=8192
> SUBCHANNELS=0.0.710C,0.0.710D,0.0.710E
To be on the safe side, hex digits for Linux shoul
Sent: Tuesday, July 20, 2010 9:23 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Can't get hipersockets to come online
I feel the uevent is not generated on-boot with ifcfg-script
Group the devices manually and check
echo 0.0.710C,0.0.710D,0.0.710E > /sys/bus/ccwgroup/drivers/qeth/group
:16 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Can't get hipersockets to come online
>
> Same command for Redhat. Didn't try that but no help. Nothing to tell me
> why it didn't come online.
>
>
>
> [r...@lssb1 /]# chccwdev -e 0.0.710C
>
> Sett
Subject: Re: Can't get hipersockets to come online
Page 98
http://www.redbooks.ibm.com/redbooks/pdfs/sg246816.pdf
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Bauer,
Bobby (NIH/CIT) [E]
Sent: Tuesday, July 20, 2010 8:16 AM
To: LINU
d luck,
Offer baruch
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Bauer,
Bobby (NIH/CIT) [E]
Sent: Tuesday, July 20, 2010 2:48 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Can't get hipersockets to come online
Just rebuild our sandbox going from
Page 98
http://www.redbooks.ibm.com/redbooks/pdfs/sg246816.pdf
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Bauer,
Bobby (NIH/CIT) [E]
Sent: Tuesday, July 20, 2010 8:16 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Can't get hipersocke
8
301-594-7474
-Original Message-
From: karlkings...@ongov.net [mailto:karlkings...@ongov.net]
Sent: Tuesday, July 20, 2010 7:58 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Can't get hipersockets to come online
Did you bring the devices online? Under SUSE, use chccwdev -e 0.0.71
Did you bring the devices online? Under SUSE, use chccwdev -e 0.0.710C
(repeat for each device)
From: "Bauer, Bobby (NIH/CIT) [E]"
To: LINUX-390@VM.MARIST.EDU
Date: 07/20/2010 07:49 AM
Subject:Can't get hipersockets to come online
Sent by:Linux on 39
Just rebuild our sandbox going from a couple of mod3's to a mod27 and of course
the latest Redhat Linux 5.5. No change on the VM side but the hsi0 interface
won't come up and I can't see why. Most frustrating because it work yesterday
before I changed disk. Obviously I've forgotten something and
It's working now.
Had to change the layer2 support for the hipersockets off and then the
device was built like the one on sles10 sp2.
Frank Skellen
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message i
I'm using SLES11 with hipersocets , it's working fine over a 2064-214 CPU
hsi0 interf its connected to a virtual lan between a couple of linux and
zVM
hsi0 Link encap:Ethernet HWaddr 02:00:00:00:00:0E
inet addr:10.1.1.19 Bcast:10.1.1.255 Mask:255.255.255.0
inet6 addr:
It's working now.
Had to change the layer2 support for the hipersockets off and then the
device was built like the one on sles10 sp2.
Frank Skellen
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message i
>>> On 6/3/2009 at 2:43 PM, Frank Skellen wrote:
> Qeth.3qacf0c: 0.0.a100: The qeth device driver failed to recover an
> error on the device
And that's all? Nothing before that which might be related? Seems odd.
Mark Post
deleting it from your computer.
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Mark Post
Sent: Wednesday, June 03, 2009 2:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: sless11 under zvm using hipersockets
>>> On 6/3/2009 at 1:43 PM, Fran
>>> On 6/3/2009 at 1:43 PM, Frank Skellen wrote:
> I am having problems with sles11 hipersockets on a z9. I have sles10
> sp2 using hipersockets just fine. When attempting the same
> configuration for suse11 I cannot get the base name hsiX interface to
> come up. I iss
Wouldn't you use
chccwdev --online 0.0.a100
On Wed, Jun 3, 2009 at 1:43 PM, Frank Skellen wrote:
> I am having problems with sles11 hipersockets on a z9. I have sles10
> sp2 using hipersockets just fine. When attempting the same
> configuration for suse11 I cannot get the
I am having problems with sles11 hipersockets on a z9. I have sles10
sp2 using hipersockets just fine. When attempting the same
configuration for suse11 I cannot get the base name hsiX interface to
come up. I issue "# echo 1 >
/sys/bus/ccwgroup/drivers/qeth/0.0.a100/online"
On Thu, 2009-04-09 at 13:18 -0400, Bauer, Bobby (NIH/CIT) [E] wrote:
> echo 0.0.710c,0.0.710d,0.0.710e > group
On Thu, 2009-04-09 at 10:34 -0400, Bauer, Bobby (NIH/CIT) [E] wrote:
> SUBCHANNELS=0.0.710C,0.0.710D,0.0.710E
You should change SUBCHANNELS value to lowercase:
SUBCHANNELS=0.0.710c,0.0.7
On Thu, 9 Apr 2009 13:18:03 -0400
"Bauer, Bobby (NIH/CIT) [E]" wrote:
> Seems Redhat doesn't have 'hwup' or /etc/sysconfig/hardware however the
> 'lsqeth' did not know about the hipersocket addresses.
Red Hat equivalent is ifup and I would guess that
/etc/sysconfig-network-scripts/ifcfg-foo
is
sda, MD 20892-5628
301-594-7474
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Rob van
der Heij
Sent: Thursday, April 09, 2009 11:00 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets on Redhat
Also try whether "hwup" of the device helps to
Also try whether "hwup" of the device helps to get it online.
On Thu, Apr 9, 2009 at 4:39 PM, Harder, Pieter
wrote:
> MODULE='qeth'
That one finally turned out for me to be missing... after I have
tried dozens of bizarre things with Mark Post at the strangest moments
in our respective nights (
rabantwater.nl
tel +31-73-6837133 / +31-6-47272537
-Oorspronkelijk bericht-
Van: Linux on 390 Port [mailto:linux-...@vm.marist.edu] Namens Bauer, Bobby
(NIH/CIT) [E]
Verzonden: donderdag 9 april 2009 16:34
Aan: LINUX-390@VM.MARIST.EDU
Onderwerp: Hipersockets on Redhat
I think I need som
I think I need somebody to look over my shoulder. I just built a new server and
cannot get the hipersockets to come online. They are working just fine on the
one one other server I have them setup on using addresses 7104-7106.
They are define in HCD as:
7100,48 IQD
In user direct:
DEDICATE
-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Scott Rohling
Sent: Monday, June 16, 2008 7:48 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Error while connecting to DB2 Connect from z/Linux over
HiperSockets
Recent responders: Just FYI - the originator of this thread indicated
while connecting to DB2 Connect from z/Linux over
HiperSockets
On Monday, 06/16/2008 at 05:49 EDT, "Evans, Kevin R"
<[EMAIL PROTECTED]> wrote:
> Not sure if this is applicable or not, but on the z/OS comm. Server
> side...113 can mean several things all generically known as EB
unless pursuant to explicit written agreement
> or government initiative expressly permitting the use of e-mail for such
> purpose.
>
> -
>
>
>
>
> "Evans, Kevin R" <[EMAIL PROTECTED]>
> Sent by: Linux on 390 Port
> 06/16/2008 12:13 PM
> Please respond to
>
390 Port
06/16/2008 12:13 PM
Please respond to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: Error while connecting to DB2 Connect from z/Linux over HiperSockets
Sounds like there isn't a listener listening or maybe a firewall in the
way.
Kevin
-Original Message--
ng to DB2 Connect from z/Linux over
HiperSockets
Kevin the errno 113
#define EHOSTUNREACH113 /* No route to host */
'Where ever you go - There you are!! '
Richard (Gaz) Gasiorowski
Global Solutions & Technology
Principal Lead Infrastructure Architect
845-773-9243 Work
845-3
PROTECTED]>
Sent by: Linux on 390 Port
06/16/2008 11:52 AM
Please respond to
Linux on 390 Port
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: Error while connecting to DB2 Connect from z/Linux over HiperSockets
Well, that's a shame, isn't it? Oh well, learn something every day.
B2 Connect from z/Linux over
HiperSockets
On Monday, 06/16/2008 at 05:49 EDT, "Evans, Kevin R"
<[EMAIL PROTECTED]> wrote:
> Not sure if this is applicable or not, but on the z/OS comm. Server
> side...113 can mean several things all generically known as EBADF:
> Socket d
On Monday, 06/16/2008 at 05:49 EDT, "Evans, Kevin R"
<[EMAIL PROTECTED]> wrote:
> Not sure if this is applicable or not, but on the z/OS comm. Server
> side...113 can mean several things all generically known as EBADF:
> Socket descriptor is not in a correct range
> Socket descriptor is already bei
:09 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Error while connecting to DB2 Connect from z/Linux over
HiperSockets
Hi
It looks like it is an issue with what the user is doing. Our DB2
Connect system guy had no trouble starting multiple DB2 Connect
sessions. So at this point it looks like everyt
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Alan Altmark
Sent: Sunday, June 15, 2008 1:07 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Error while connecting to DB2 Connect from z/Linux over
HiperSockets
On Saturday, 06/14/2008 at 04:34 EDT, "Martin,
On Saturday, 06/14/2008 at 04:34 EDT, "Martin, Terry R. (CMS/CTR) (CTR)"
<[EMAIL PROTECTED]> wrote:
> Yes, I can PING the 158.73.207.45 address of this Linux guest and have
> actually sent data. The problem is when they try to SH to open another
> connection they receive the error I mentioned. Thi
.
Thanks, Terry
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Alan Altmark
Sent: Friday, June 13, 2008 5:22 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Error while connecting to DB2 Connect from z/Linux over
HiperSockets
On Friday, 06/13/2008 at 04:59 EDT
On Friday, 06/13/2008 at 04:59 EDT, "Martin, Terry R. (CMS/CTR) (CTR)"
<[EMAIL PROTECTED]> wrote:
> While trying to start multiple DB2 connections we receive the following
> message:
> SQL30081N A communication error has been detected. Communication
> protocol being used: "TCP/IP". Communicatio
Communication function
>
> detecting the error: "connect". Protocol specific error code(s): "113",
> "*",
>
> "*". SQLSTATE=08001
>
>
>
>
>
> Basically we can have only one connection at a time. Is there anything
>
cted: "158.73.207.45". Communication function
detecting the error: "connect". Protocol specific error code(s): "113",
"*",
"*". SQLSTATE=08001
Basically we can have only one connection at a time. Is there anything
else we need to do on the Linux
Mark Post wrote:
On Thu, Jul 26, 2007 at 3:56 PM, in message
<[EMAIL PROTECTED]>, "Ayer,
Paul W" <[EMAIL PROTECTED]> wrote:
-snip-
Should I add a DNS z/Linux system inside the z/VM as a first check that
would resolve the same name to a 12
Then if not found there somehow go out to the network D
> Doesn't this second entry conflict with the other CNAME entry? Does
this
> mean you have to have two DNS servers to implement it this way?
If it's in a different zone file, no, because if a user specifies an
unqualified vm1foo01 (which I think is what he's asking for), the
current zone context i
>>> On Fri, Jul 27, 2007 at 3:04 PM, in message
<[EMAIL PROTECTED]>, Robert J
Brenneman <[EMAIL PROTECTED]> wrote:
-snip-
> Doesn't this second entry conflict with the other CNAME entry? Does this
> mean you have to have two DNS servers to implement it this way?
In the general case you only do t
> After I sent the note I was thinking that too. Now how to I say FTP
XYZ
> and make it use one path or the other.
The method I suggested allows that exact thing to work seamlessly.
--
For LINUX-390 subscribe / signoff / archive
On 7/27/07, David Boyes <[EMAIL PROTECTED]> wrote:
>
>
> That's what CNAME records in the DNS are for.
>
>
vm1foo01-eth0 IN A 123.45.67.89
> vm1foo01-hsi0 IN A 10.11.12.13
> vm1foo01IN CNAME vm1foo01-eth0
>
> In the reverse
Thanks Mark,
After I sent the note I was thinking that too. Now how to I say FTP XYZ
and make it use one path or the other.
Oh well, the users and applications will need to be really flexible
since we plan to be able to move an instance between more than one CPU
so sometimes the Hipersockets DNS
>>> On Fri, Jul 27, 2007 at 11:08 AM, in message
<[EMAIL PROTECTED]>, "Ayer,
Paul W" <[EMAIL PROTECTED]> wrote:
> This seems to work fine.
> Please tell me where I may be in error or have a possible problem
> waiting to happen.
-snip-
> pings and trace routes now work fine via the path they sho
> Since this is an internal only network the ip address should not
matter
> at all (my thought anyway)
Oh, it matters a lot. That's why there are reserved address ranges of
differing sizes for this kind of stuff. You *will* have problems if you
do this.
Classic example: Sun used to publish examp
> Lots of systems get really upset if you try to assign multiple
hostnames
> to
> the same tcpip stack.
That's what CNAME records in the DNS are for.
I create a DNS forward and reverse for each interface (canonical
name-interface, eg foo-eth0, foo-hsi0, etc.). The "hostname" that I
configure as
Lots of systems get really upset if you try to assign multiple hostnames to
the same tcpip stack. I set up two different DNS domains for this type of
configuration.
Each host on the network has only one hostname:
Linux1
Linux2
etc
Each host is actually a member of two domains:
my.external.net:
This seems to work fine.
Please tell me where I may be in error or have a possible problem
waiting to happen.
>From DNS name is agzls008 with and IP address of 192.168.32.139
To DNS name is agsl013 with and IP of 192.168.127.5
Background
On agzls008 I have this ifconfig
Hi Mike,
Since this is an internal only network the ip address should not matter
at all (my thought anyway), plus if we were to use a real routable
address that could become a problem if a session to that address were
made over the
OSA (not hipersockets path) ... ??? but I guess if were to
Paul,
> setup the hipersocket network as 12. for testing and so it stands out
Would it be better to use 10.? 12. is a real class A IP address range. 10.
is the private class A range (RFC 1918 I believe).
"Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061
---
>>> On Thu, Jul 26, 2007 at 3:56 PM, in message
<[EMAIL PROTECTED]>, "Ayer,
Paul W" <[EMAIL PROTECTED]> wrote:
-snip-
> Should I add a DNS z/Linux system inside the z/VM as a first check that
> would resolve the same name to a 12
> Then if not found there somehow go out to the network DNS. Should
Good day,
I have seen a few notes here before but they were mostly for not working
links.
Here is my problem have z/linux working for both normal in/out the OSA
to the network and also have now
setup the hsi0 for Hipersockts links.
Pings, traceroutes, ftp's, ssh's all work fine using addresses
On Monday, 07/09/2007 at 11:10 AST, Kim Goldenberg
<[EMAIL PROTECTED]> wrote:
> HOME
> xxx.yyy.1.101 HIPER50
Make sure you are using chpid 50 on Linux.
1. CP Q V xxx (where xxx is the vdev of the HiperSocket). Note the
SUBCHANNEL number.
2. CP D SCHIB nnn (where nnn is the subchannel number)
3.
Alan Altmark wrote:
On Monday, 07/09/2007 at 11:10 AST, Kim Goldenberg
You need to display the routing table on z/OS. Since you're not
[shouldn't be] running OSPF or RIP on the HiperSocket there will be an
INTERFACE statement in omproute's configuration. If there isn't, then it
is defaulting a
> > What are the IP addresses and subnet masks on the z/OS HiperSocket
> interfaces?
> ; ***
> ; HIPERSOCKET CHIPID 50
> ; ***
> DEVICE IUTIQD50 MPCIPA
> LINK HIPER50 IPAQIDIO IUTIQD50
> HOME
>zzz.yyy.72.82 OSA2
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:224 (224.0 b)
-snip-
What is the MTU size specified on the z/OS side of the HiperSockets?
-
On Monday, 07/09/2007 at 10:17 AST, Kim Goldenberg
<[EMAIL PROTECTED]> wrote:
> xxx.yyy.1.0 0.0.0.0 255.255.255.0 U 0 0 0 hsi0
I haven't been following this in detail, but I see two possibilities:
1. The OTHER system is configured INcorrectly. Remember that it is a
two-way stree
David Boyes wrote:
ifconfig
eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:02
inet addr:xxx.yyy.40.21 Bcast:xxx.yyy.40.255
Mask:255.255.255.0
hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:xxx.yyy.1.103 Bcast:xxx.yyy.1.255
Mask:255.255.255.0
OK,
David Boyes wrote:
All the basics look good.
Thanks.
Are you explicitly specifying the IP address of the other host
(xxx.yyy.1.zzz)?
Specifying it where? in the ping? then yes.
If you're using the name, then that probably maps to
the .40 address (unless you're really good, and gave the .1.z
UP BROADCAST RUNNING NOARP MULTICAST MTU:8192 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:224 (224.0 b)
>
> ifconfig
> eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:02
> inet addr:xxx.yyy.40.21 Bcast:xxx.yyy.40.255
> Mask:255.255.255.0
>
> hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:xxx.yyy.1.103 Bcast:xxx.yyy.1.255
Mask:255.255.255.0
OK, adapte
d.
I once again have installed the OSA adapter (needed for NFS install). I
also reinstalled the Hipersockets definition. information follows:
eth0 = OSA adapter
hsi0 = Hipersockets
ifconfig
eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:02
inet addr:xxx.yyy.40.21 Bcast:xxx.yyy.40
Mark Post wrote:
On Fri, Jun 29, 2007 at 3:43 PM, in message
<[EMAIL PROTECTED]>, Kim Goldenberg
<[EMAIL PROTECTED]> wrote:
We are starting our Linux POC and all has been going well. Until I got
to the Hipersockets, that is.
-snip-
z/OS -- OSA -- network -- OSA -- Linux
: Linux on 390 Port on behalf of Kim Goldenberg
Sent: Mon 7/2/2007 12:13 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets Conundrum
David Kreuter wrote:
> also check that the MTU sizes match.
> David
>
Hi Dave - First thing I checked.
--
Kim Goldenberg
Systems Programmer I
State of
David Kreuter wrote:
also check that the MTU sizes match.
David
Hi Dave - First thing I checked.
--
Kim Goldenberg
Systems Programmer I
State of NJ - OIT
609-777-3722
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
For LINUX-390 subsc
Rich Smrcina wrote:
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?
No, Hipersockets on 172.20.1/24 and OSAs on 172.20.40/24 via vswitch.
Kim
--
Kim Goldenberg
Systems Programmer
What does your routing table look like?
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
>>> On Fri, Jun 29, 2007 at 3:43 PM, in message
<[EMAIL PROTECTED]>, Kim Goldenberg
<[EMAIL PROTECTED]> wrote:
> We are starting our Linux POC and all has been going well. Until I got
> to the Hipersockets, that is.
-snip-
> z/OS -- OSA -- network -- OSA -- Linux (o
also check that the MTU sizes match.
David
-Original Message-
From: Linux on 390 Port on behalf of Rich Smrcina
Sent: Fri 6/29/2007 11:51 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Hipersockets Conundrum
So are your OSA devices and Hipersocket devices all on the same network?
In
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
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
cc
<[EMAIL PROTECTED]
IST.EDU> Asunto
Re: Help with Linux - to VSE
On Friday, 04/20/2007 at 04:36 ZE2, Aristarc Diez Redorta
<[EMAIL PROTECTED]> wrote:
> hsi0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> inet addr:192.68.24.1 Bcast:192.68.24.255 Mask:255.255.255.0
> inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
> UP BROADCAST RUNNING NOARP MULTICAST MT
>>> On Fri, Apr 20, 2007 at 11:53 AM, in message <[EMAIL PROTECTED]>, Rich
Smrcina <[EMAIL PROTECTED]> wrote:
> Clearly I didn't read far enough... :)
The only reason I read as far as I did, was because I had no idea what in the
world I was looking at until I got to the end. Fresh set of eyes,
Clearly I didn't read far enough... :)
Mark Post wrote:
On Fri, Apr 20, 2007 at 10:36 AM, in message
<[EMAIL PROTECTED]>,
Aristarc Diez Redorta <[EMAIL PROTECTED]> wrote:
Here is the ifconfig:
-snip-
The very end of your TCP/IP start up log shows successful pings:
20070420 162754.71 0012:
>>> On Fri, Apr 20, 2007 at 10:36 AM, in message
<[EMAIL PROTECTED]>,
Aristarc Diez Redorta <[EMAIL PROTECTED]> wrote:
> Here is the ifconfig:
>
-snip-
The very end of your TCP/IP start up log shows successful pings:
20070420 162754.71 0012: IPC108I ICMP Echo request has been received from:
19
PROTECTED]
IST.EDU> Asunto
Re: Help with Linux - to VSE
Hipersockets
20/04/2007 14:58
Por favor,
responda a
Do the interfaces come up on both Linux and VSE. Send the output from
the Linux ifconfig and your VSE TCP/IP config and startup messages.
Aristarc Diez Redorta wrote:
Hi Rick,
we cannot ping from Linux to VSE and from Vse to Linux.
This is the first time we're trying to configure it.
TIA.
Ari
There is nothing special that has to be done in Linux to access VSE via
Hipersockets. If you have Hipersockets configured on the system, attach
the device sets to each Linux and VSE and configure the interfaces.
One thing to remember on the VSE side is that when adding the device you
need to
Hi all,
can anyone help me or show me how to configure Linux Hipersockets to access
VSE Hipersockets?
TIA.
Aris.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the
th Linux - to VSE
Hipersockets
20/04/2007 14:22
Por favor,
responda a
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
There is nothing special that has to be done in
Is anything else on the Hipersocket network that you can ping?
Maybe try this route:
DEFINE ROUTE,ID=HIPERS,LINKID=OSAA,IPADDR=192.68.24.0,-
GATEWAY=192.68.24.1
You may want to post this to vse-l. CSI monitors vse-l can may respond
there.
Aristarc Diez Redorta wrote:
Here is the ifconfig:
Sorry - been so long since I've done this some things have fallen through
the memory cracks. I forgot
3a) (on zLinux) catalog database at node
5a) (on XP client) catalog database at node
and the connect is
connect to user using
http://www-
128.ibm.com/developerworks/db2/library/techarticl
> And if the DB/2 connect software is on the client, why not connect
> directly to z/OS DB/2? Going through Linux would seem to be an
> unnecessary step.
I'd tend to agree, but it may be a solution to a political problem (ie,
not permitting direct connections to mainframe (defining mainframe =
z/O
Typically to do this you need to
1) create a DB2 instance on the DB2 Connect server. Normally this would have
been done
during the installation process unless the installer had specifically skipped
the step.
2) attach to the instance on the zLinusx system
3) catalog tcpip node remote 192.168.1.
And if the DB/2 connect software is on the client, why not connect
directly to z/OS DB/2? Going through Linux would seem to be an
unnecessary step.
Harold Grovesteen
David Boyes wrote:
Trying my best to answer your question - but this is uncharted waters
for me.
What you want to do is forward
> Trying my best to answer your question - but this is uncharted waters
> for me.
>
> What you want to do is forward the DB/2 Connect ports to the z/OS DB/2
> instance, right?
> No I don't think so, because isn't that what DB/2 Connect
> provides. Some how I have got to get the DB/2 Connect
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
David Boyes
Sent: Friday, March 02, 2007 5:12 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DB2 Connect; using Linux as a gateway to mainframe LPAR via
hipersockets
> The only piece of information I h
> The only piece of information I have been able to uncover - states
> "DB2COMM and SVCENAME" are setup automatically" but it seemed to me
only
> to apply with the installation of DB2 not DB2 Connect. It is not my
> intention to run DB2 on the zLinux system. I only want it to serve as
a
> gateway
>>> On Fri, Mar 2, 2007 at 5:18 PM, in message
<[EMAIL PROTECTED]>, "Clark,
Douglas" <[EMAIL PROTECTED]> wrote:
-snip-
> The only piece of information I have been able to uncover - states
> "DB2COMM and SVCENAME" are setup automatically" but it seemed to me only
> to apply with the installation
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Friday, March 02, 2007 1:48 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DB2 Connect; using Linux as a gateway to mainframe LPAR via
hipersockets
>>> On Thu, Mar 1, 2007 at 7:
>>> On Thu, Mar 1, 2007 at 7:18 PM, in message
<[EMAIL PROTECTED]>, "Clark,
Douglas" <[EMAIL PROTECTED]> wrote:
-snip-
> Output from "iptables - L - n" as executed on the zLinux system.
>
> techlnux:~ # iptables - L - n
> Chain INPUT (policy ACCEPT)
> target prot opt sourc
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Thursday, March 01, 2007 3:06 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DB2 Connect; using Linux as a gateway to mainframe LPAR via
hipersockets
>>> On Thu, Mar 1, 2007 at 5:
>>> On Thu, Mar 1, 2007 at 5:52 PM, in message
<[EMAIL PROTECTED]>, "Clark,
Douglas" <[EMAIL PROTECTED]> wrote:
-snip-
> What does "tracert - d 10.128.24.232" from the Windows system show?
> F:\>tracert - d 10.128.24.232
>
> Tracing route to 10.128.24.232 over a maximum of 30 hop
a gateway to mainframe LPAR via
hipersockets
Mark Post wrote:
>>>> On Thu, Mar 1, 2007 at 4:40 PM, in message
> <[EMAIL PROTECTED]>,
> "Clark, Douglas" <[EMAIL PROTECTED]> wrote:
>> Here are the answers to your question.
>>
>>
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Thursday, March 01, 2007 1:51 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DB2 Connect; using Linux as a gateway to mainframe LPAR via
hipersockets
>>> On Thu, Mar 1, 2007 at 4:
Mark Post wrote:
On Thu, Mar 1, 2007 at 4:40 PM, in message
<[EMAIL PROTECTED]>, "Clark,
Douglas" <[EMAIL PROTECTED]> wrote:
Here are the answers to your question.
What IP addresses are you using for the two ends of the HiperSocket
connection?
zLinux IP Addr: 10.128.24.232
z/O
>>> On Thu, Mar 1, 2007 at 4:40 PM, in message
<[EMAIL PROTECTED]>, "Clark,
Douglas" <[EMAIL PROTECTED]> wrote:
> Here are the answers to your question.
>
> What IP addresses are you using for the two ends of the HiperSocket
> connection?
> zLinux IP Addr: 10.128.24.232
> z/OS IP Add
101 - 200 of 492 matches
Mail list logo
