Re: Telnet Server -- MIDRANGE-L

I maybe confused but I thought you wanted to connect to two different ports
and do telnet, and if it was on one of the ports do something special. And
I thought the problem was you could not start telnet on two different
ports. With the socket program you could bind on a port of your choice as
long as it is unused. Here is what I was thinking. You would leave telnet
running on its normal port. your socket program would run on some other
port. You would move your exit program logic into your socket program, then
your socket program would pass the data out to the telnet server. That is
what a proxy server program does, takes data in, maybe a little checking of
the data, and then passes it along. Since I do not know what you are doing
in the exit program I may not be seeing the problem.

Here is another thought, instead of port how about two IP addresses?

And do dumb terminals use the telnet server?

John Ross

At 03:39 PM 9/2/01 -0500, you wrote:
>Using a socket program was a very good idea. I'd considered it once, but
>wasn't sure where to go with it. I went out to Scott's site and took a look
>at his tutorial.  Very, VERY! nice work on his part.  Excellent tutorial on
>how to use sockets!
>
>I think that using my own socket server would work if there was a way to
>call the AS/400's telnet emulation programs manually via the socket server.
>In otherwords, if I could use a socket to bind to a port of my choice, and
>then once I'm on that remote system, have the AS/400's telnet programs
>(those ran normally by the *TELNET server) initiated, then this approach
>would work really well.
>
>Without being able to call the same programs as used by the *TELNET server,
>I'd have to write my own telnet programs, and that's waaay more work than I
>want to tackle!
>
>And, keep in mind (not sure if I'd said this in my previous posts or not...)
>that whatever solution I end up with, it'll have to work with AS/400
>sessions initiated by both PC clients and dumb terminals.
>
>Anyone know where I can find documentation on the programs used by the
>*TELNET server?
>
>Actually, I don't even know if I'd be able to use those programs anyway,
>even if I did know which programs to call and which parms to pass as they
>probably run in the SYSTEM state and would therefore be inaccessible to my
>apps.
>
>This will all be moot in about a year to a year and a half anyway as this
>whole software package is being redesigned to use servlets. However, until
>that time, this is a nut that I need to find a way to crack, one way or
>another.
>
>This would be so much easier if I could just retrieve the remote data and
>bring it back to the local system rather than being forced to start a 5250
>session on that remote system.
>
>Oh well....I'll think of something.