Re: Telnet Server

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.


----- Original Message -----
From: "John Ross" <jross-ml@netshare400.com>
To: <midrange-l@midrange.com>
Sent: Friday, August 31, 2001 10:04 PM
Subject: RE: Telnet Server


> I have not read all of this thread.
>
> But how about writing a socket program.
> See  http://klement.dstorm.net/rpg/socktut/ip_proxy.html  for a program
> that is close to what you might need. It allows client connections on two
> ports you would need to allow connections on one port  and then start a
> connection on your telnet port. You would have to move your exit program
> logic into this new program.
>
> John Ross
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>