>> >> On Tue, Feb 14, 2023 at 8:47 PM Steve David <steve.davids...@gmail.com> >> wrote: >> >> > Hello, >> > >> > We had some issue setting up NJE over Ip, It's a multi-stack environment >> > (TCPIPA1 & TCPIPA2), we had problem using(Nat) ip and port 175. Netsrv1 >> > couldn't bind to port 175. We did verified that port 175 was not in use >> > from both the stacks. >> > >> > IAZ05451 NETSRV1 Error encountered in function >> > bind() - EDC81161 Address not available. >> > >> > IAZ05011 NETSRV1 Bind for the server socket failed,TCP/IP rc: 1116 >> > >> > IAZ05361 NETSRV1 NJETCP SERVER RECEIVED A PURGE REQUEST >> > >> > IEA9891 SLIP TRAP ID=X13E Matched. JOBNAME=JES2S001, ASID=00CB. >> > >> > IAZ05161 NETSRV1 Error while closing client socket,TCP/IP rc: 113 >> > >> > IEF4041 IEESYSAS-ENDED - TIME=07.07.55 >> > >> > IEF1961 IEF1421 IEESYSAS JES2S001-STEP WAS >> > EXECUTED-COND CODE 0000 >> > >> > Thanks
Depends on your IP settings (protecting lower ports etc.) or there could be other RACF protections involved. Easiest thing to do is code it in your TCPIP profile under PORT. That really should be done anyway so some other unexpected task doesn't try using it. 175 TCP JES2S* ; NJE TCP Some other things I ran into when I implemented it years ago was at some version of when it became available, there should have been an update to /etc/services. vmnet 175/tcp # JES NJE over TCP/IP I honestly don't know if that not being there causes a problem or not but it was something I checked for since I knew about it and in my environment with 30 LPARs I found it wasn't done for one company's LPARs. Best Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
