IAZ0545I NETSRV1 Error encountered in function connect() - EDC8128I
Connection refused.
IAZ0543I NETSRV1 TCP/IP connection with IP Addr: 10.100.5.73 Port: 175
ended due to TCP/IP error, rc: 1128
The "connection refused" error can indicate a lack of resources on the
receiving (z/VM) node. Are you sure that ALL of the necessary RSCS resources
are available/started.
Since Telnet and ping are working, you must have basic connectivity.
Is there a process listening on port 175 on the z/VM node??
Could try "telnet 10.100.5.73 175" (from the z/OS LPAR) to see if you
get a connection!!
Hth
Tony
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of McCabe, Ron
Sent: Wednesday, February 06, 2019 12:59 PM
To: [email protected]
Subject: Re: How can I get reports in the Output Queue in SDSF to print
[[ SEI WARNING *** This email was sent from an external source. Do not open
attachments or click on links from unknown or suspicious senders. *** ]]
Vince,
Thanks for letting me know about using a FICON CTC...the problem was when we
ordered the z13s we didn't order enough FICON adapters...guess our research was
not through enough.
As far as where the problem actually is...I believe it is the network to but
I'm losing that battle and it is because my boss is a networking guy who
supports the networking team over the mainframe team.
I can PING from z/VM to z/OS and vice versa successfully and I have done a
telnet from z/OS to z/VM successfully. I'm not familiar with ICMP and/or
TRACERTE so I will have to do research on how to check/execute them.
When I start NETSRV1 it says it is active in ASID=004D as NAME=JES2S001 and yes
the JES line is started, however I get an error when starting the socket and
the error is...
IAZ0545I NETSRV1 Error encountered in function connect() - EDC8128I Connection
refused.
IAZ0543I NETSRV1 TCP/IP connection with IP Addr: 10.100.5.73 Port: 175 ended
due to TCP/IP error, rc: 1128
Thanks,
Ron McCabe
Mutual of Enumclaw
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Vince Getgood
Sent: Wednesday, February 06, 2019 1:15 AM
To: [email protected]
Subject: Re: How can I get reports in the Output Queue in SDSF to print
Ron,
AFAIK, you are correct regarding a virtual CTC, but you can still define a real
FICON CTC - I think I'm correct in saying you just need one spare FICON port,
unlike ESCON, where you needed two, and a cable between them.
Assuming nothing has changed on the mainframe, and you are running JES2, this
definitely sounds like a network issue.
I'm sure IBM will help, but, in the meantime...
Basics first. Can you ping z/VM from z/OS and vice versa? Of course ICMP
might be blocked, so you could also try TRACERTE ipaddress from both systems.
Maybe also try TELNET, just to prove both systems can see each other.
Is your JES NETSRV address space up (something like JES2S001)?
Is the JES line started?
What happens when you issue $SN,N=your z/VM node number (or possibly
$SN,SOCKET=your z/VM socket number) on the z/OS system?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
Confidentiality Notice: This e- mail and all attachments may contain
CONFIDENTIAL information and are meant solely for the intended recipient. It
may contain controlled, privileged, or proprietary information that is
protected under applicable law and shall not be disclosed to any unauthorized
third party. If you are not the intended recipient, you are hereby notified
that any unauthorized review, action, disclosure, distribution, or reproduction
of any information contained in this e- mail and any attachments is strictly
PROHIBITED. If you received this e- mail in error, please reply to the sender
immediately stating that this transmission was misdirected, and delete or
destroy all electronic and paper copies of this e-mail and attachments without
disclosing the contents. This e- mail does not grant or assign rights of
ownership in the proprietary subject matter herein, nor shall it be construed
as a joint venture, partnership, teaming agreement, or any other formal
business relationship.
----------------------------------------------------------------------
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
