Dave, There must be a reason why are you using the hipersocket IP address and not just the default TCPIP stack IP address and perhaps this is where your problem lies. Could this just be a simple TCPIP routing issue? It sounds like you know you have a route from this z/OS system to 192.169.1.3 (using the hipersocket).
However, when NJE starts a session it gives the packet an origin IP address. The value of this is completely controlled by you (or your network guy). It could be the default for this TCPIP stack or it could be something you have specified on a SRCIP statement or in a BIND parameter. Is this origin IP address routable from the other z/OS? When sending a response to your signon request it will send it back to this origin IP address so it must have a route to it. If not the packet will go who knows where. Maybe the default route out the OSA where it hits a firewall. If you are planning on using 192.168.1.x for all NJE communication then maybe you need to specify each z/OS system's hipersocket IP address as the origin. Alternatively, don't use SOURCEVIPA at all for the hipersocket interface. Of course if this is your problem the solution depends completely upon your network design and where packets might route during interface outages. Regards, Alan. -----Original Message----- From: Gibney, Dave [mailto:[email protected]] Sent: 01 November 2017 10:51 pm Subject: Moving from NJE over ESCON CTC to IP I think I've done an equivalent set of JESPARMS, but I get this $HASP568 NODE=AISDEVL - AUTOMATIC CONNECT (SOCKET=AISDEVL) IAZ0543I NETSRV4 TCP/IP connection with IP Addr: 192.168.1.3 Port: 175 Initiated IAZ0543I NETSRV4 TCP/IP connection with IP Addr: 192.168.1.3 Port: 175 Successful IAZ0543I NETSRV4 TCP/IP connection with IP Addr: srcpos02.ad.wsu.edu Port: 175 ended due to failure of NJETCP Signon to complete within allotted time For all connection. The 192.168.1 network is over Hipersocket Undoubtably, I am missing something simple in the TFM Dave Gibney Information Technology Services Washington State University ---------------------------------------------------------------------- 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
