×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have a client that is running a client server system where the iSeries is
a client. When they try to start the job on the iSeries, they are getting a
failure trying to access the specified port. It is my understanding that
the package previously worked and when they did an IPL, it stopped working.
There were supposedly no other configuration changes to the iSeries or the
network. That sounds really strange to me. Unfortunately, at this time I
only have a message that the connection failed. I don't know if it was the
open or the bind or something else that it didn't like. We are adding some
additional logging to the program to try to be a better message than
"connection failed".
In the meantime, I had them do a NETSTAT option 3 and F14 to see the ports
and they said the port in question does not show anything using it. Is
there anything else that anyone can suggest to look at that might show me
what is causing the failure?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
