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 email@example.com.
I suggest you tell your customers using Tomcat on IBM i to ensure that they have specified HOSTSCHPTY(*LOCAL), and document it in your product documentation.
All the best,
Mark S. Waterbury
On Friday, April 15, 2022, 04:07:33 PM EDT, James H. H. Lampert via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Regardless of how a system can end up with two STRTCPs, it turned out
not to be the issue here. I think we've mentioned it to the customer,
somewhere in our report.
What does worry me is what *else* could be affected by this odd
combination of "HOSTSCHPTY(*REMOTE)" and a house DNS server responding
to "LOCALHOST" and "LOOPBACK."
And it puzzles the Hell out of me how and why such a combination would
arise in the first place. I can grant that there might be some
legitimate reason to allow DNS to override the Host Table (even if I
cannot imagine what that reason might be), but having a DNS respond to
"LOCALHOST" or "LOOPBACK" sounds downright ludicrous, and as I
discovered, the combination of the two is a recipe for disaster.
As an Amazon Associate we earn from qualifying purchases.