Guys,
Thanks for the input.
I was hoping to avoid "Terminal Services/VNC" type gimmickry.
But then, I'm not too up on TELNET. I'm an old Twin-Ax guy.
Christopher Wyatt
Agility, Inc.
cwyatt@xxxxxxxxxxxxxxx
(440) 546-9290 x3008
-----Original Message-----
------------------------------
message: 6
date: Wed, 23 May 2007 10:45:09 -0700
from: "Dan Hogan" <Dan.Hogan@xxxxxxxxxxxx>
subject: RE: Terminal emulation over spotty network connection...
Chris,
By their nature, wireless networks are not as reliable as wired
networks. TCP and TELNET were designed for wired networks. Since TCP
and TELNET are chatty, if the TELNET server looses contact with the
client, it will cause the problems that you are describing. If you are
open to a commercially available solution, we have a product that will
help you.
http://www.stay-linked.com
Dan....
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Wyatt
Sent: Wednesday, May 23, 2007 8:32 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Terminal emulation over spotty network connection...
Hello all,
I've searched for information about this and I haven't come up with
much.
I have a situation where user are roaming with tablet PCs and a WiFi
connection.
We are using iSeries Access green screen emulation.
When the users are moving around, they will occasionally lose the
network connection when they go from one WiFi zone to another.
How can I set up the emulation sessions so that they don't drop?
I know about QDEVRCYACN and QDSCJOBITV. But tweaking them still seems
to present an unacceptable amount of recovery actions by the end users.
I would like there to be NO recovery actions by the users.
(I might be OK if the connection went down while they were system
inhibited, but if the session is just sitting there...)
Thanks in advance.
Christopher Wyatt
midrange.com
