Re: Telnet Server

Great ideas, and I may end up going with a solution like this if I have to.
However, if at all possible, I have to make this functionality available to
users working off old clunker 3487 (or whatever) dumb terminals too.

There may not be a good solution for this, and I can live with that too. I
just have to convince others of it and to do that, I have to first exhaust
every other possibility.

Besides...this is sort of fun poking into new territory.  I like the kinds
of problems that don't lend themselves to simple solutions!


----- Original Message -----
From: "Bob Buchanan" <BobbyB@camstar.com>
To: <midrange-l@midrange.com>
Sent: Sunday, September 02, 2001 4:25 PM
Subject: Re: Telnet Server


> It is still Host On Demand.
>
> http://www-4.ibm.com/software/webservers/hostondemand/
>
> -Bob Buchanan
>
> > Jeffrey Silberberg wrote:
> >
> > Shannon,
> >
> >             Why not a redirect into IBM's or Mocha's Web based 5250
> > emulators ..
> > then you can control outside access, and drive a data stream RQST that
> >
> > has all the RQST parms you need...
> >
> > It used to be called Host On Demand, not sure what it's called today
> > with
> > all the
> > repackaging going on..
> >
> > Jeffrey M. Silberberg
> > Independent Consultant
> > CompuDesigns, Inc.
> > Atlanta, GA.
> >
> > AS SOON AS I KNOW THE ANSWERS
> > THEY CHANGE THE QUESTIONS
> >
> > ----- Original Message -----
> > From: Shannon O'Donnell <shannono@janodata.com>
> > To: <midrange-l@midrange.com>
> > Sent: Sunday, September 02, 2001 4:39 PM
> > Subject: 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.
> > > >
> > > >
> > >
> > > _______________________________________________
> > > 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.
> > >
> >
> > _______________________________________________
> > 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.
> _______________________________________________
> 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.
>
>