The problem was solved using Firewall definitions. Apparently not all people who work on firewall are created equal. Gadi
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Colin Paice Sent: יום ה 27 יולי 2023 12:03 To: [email protected] Subject: Re: Network question Gadi, I was not sure of the problem, and where the specific started task comes in. Can you ping the RHEL server from z/OS? If the ping fails it could be due to two reasons 1. z/OS does not know about the RHEL address 2. The ping request got to RHEL, but RHEL does not know the route to get back to z/OS. TRACERTE ( on z/OS) and traceroute ( on RHEL) may help in this On Ubuntu traceroute gave me $ traceroute 10.1.1.2 traceroute to 10.1.1.2 (10.1.1.2), 30 hops max, 60 byte packets 1 10.1.0.3 (10.1.0.3) 0.285 ms 0.250 ms 0.167 ms 2 zos (10.1.1.2) 5.121 ms 2.271 ms 4.334 ms The first hop ( 1) went via 10.1.0.3, the second hop (2) went via 10.1.1.2 on z/OS TSO NETSTAT HOME gave me Home address list: LinkName: ETH1 *Address: 10.1.1.2* Flags: Primary on z/OS tso tracerte 10.1.0.2 gave me CS V2R4: Traceroute to 10.1.0.2 (10.1.0.2): 1 10.1.1.1 (10.1.1.1) 1 ms 1 ms 1 ms 2 10.1.0.2 (10.1.0.2) 2 ms 1 ms 1 ms so the first hop(1) went via 10.1.1.1, the second hop went via 10.1.0.2 (from 10.1.1.1) Colin On Thu, 27 Jul 2023 at 09:15, Gadi Ben-Avi <[email protected]> wrote: > Hi, > Our z/OS system has a physical ip address and a VIPA address. > We set TCPSTACKSOURCEVIPA so that the origin address is always the > VIPA address. > > We have a new server that is in the same network as the z/OS system's > physical address. We need to send information from z/OS to this server. > Since z/OS uses the VIPA address, the information does not get through. > > Is there a way to tell TCP/IP on z/OS to use the physical address form > a specific Started Task? > > Is there any other way to solve this problem? > > We are z/OS v2.3. > The server is running RHEL 9.0. > > Thanks > > Gadi > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
