× 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.



If you can get to just one as400 via telnet, you can then telnet from that
system 5250 job to the other as400's.  At a command line type telnet (system
name or ip address)


-----Original Message-----
From: Vernon Hamberg [mailto:vhamberg@attbi.com]
Sent: Friday, July 26, 2002 10:27 PM
To: midrange-l@midrange.com
Subject: Re: Changing ports used by TCP/IP servers


Thanks, John, I'll look at these things.

I agree, having everything in triplicate is daunting. I think there'll be
only 1 that'll be opened up for ftp - this'd be for customer uploads, esp.,
plus our own work remotely. Then we'd get on the system ourselves and ftp
internally, as needed, so there's really no NEED for different ports here.

telnet on different ports isn't so bad, since we mostly use this for PC5250
or other emulation, and those have the capability to set ports, so that's a
one-time thing. The same for our products, in which you set up the ports
yourself anyway. The other one that matters to me now is the Websphere Dev
Studio client stuff - again, you set these up once and then don't need to
enter them every time.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.