×
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.
On 20/05/2009, at 6:41 AM, Peter Dow wrote:
Well, they got a unsatisfying answer from IBM. the HOSTSCHPTY parm on
the CHGTCPDMN command was set to *REMOTE; when they changed it to
*LOCAL, ROI's software worked.
That suggests to me that something in the network DID change--despite
assurances to the contrary.
When *REMOTE is set the system will first use the named DNS servers to
resolve TCP names. Either the name in question has been removed from
those servers or the servers themselves are unreachable.
When *LOCAL is set the system will check the local hosts table first.
In this case that must satisfy the request
In both cases, if the preferred method fails to resolve the name, the
secondary method should be used but perhaps it is taking so long to
perform the *REMOTE that things time-out before *LOCAL is checked?
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
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
