The only other thing that I can think of is an entry in the
/etc/services or equivalent!!!
vmnet 175/tcp # JES NJE over TCP/IP
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Gibney, Dave
Sent: Wednesday, November 01, 2017 4:45 PM
To: [email protected]
Subject: Re: Moving from NJE over ESCON CTC to IP
All ove the internal Hipersocket inside the CEC network.
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Cieri, Anthony
> Sent: Wednesday, November 01, 2017 1:44 PM
> To: [email protected]
> Subject: Re: Moving from NJE over ESCON CTC to IP
>
> Is the new IP path traversing any Firewalls???
>
> If so, Port 175 will need to be opened between the end points!
>
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Gibney, Dave
> Sent: Wednesday, November 01, 2017 4:38 PM
> To: [email protected]
> Subject: Re: Moving from NJE over ESCON CTC to IP
>
> Using EJES,
> LINES -- DELENN Line Status
> ------------------------------------------------------------------
> ------------------------- Row 1 of
> Cmd Device Status Node Work-Selection Line-Limit Page-Limit JobName
> JobID Owner CurLines TotLines ApplID Unit
> sss ssssssss/ssssssss ssssssss ssssssssssssssss ssssssssss ssssssssss
> ssssssss ssssssss ssssssss ssssssss ssssssss ssssssss ssss
> LNE1 ACTIVE
> TCP
> LNE2 ACTIVE
> TCP
> LNE3 ACTIVE
> TCP
> LNE4 ACTIVE
> TCP
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List
> > [mailto:[email protected]] On Behalf Of Cieri, Anthony
> > Sent: Wednesday, November 01, 2017 1:15 PM
> > To: [email protected]
> > Subject: Re: Moving from NJE over ESCON CTC to IP
> >
> > Dave,
> >
> > My first thought would be to check for some "available" UNIT=TCP
> > Jes2 lines.
> >
> > Hth
> > Tony
> >
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List
> > [mailto:[email protected]] On Behalf Of Gibney, Dave
> > Sent: Wednesday, November 01, 2017 3:51 PM
> > To: [email protected]
> > 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
>
> ----------------------------------------------------------------------
> 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
