Re: Timeouts

Sorry, Brendan; right you are!

In fact, your suggestion was one that seems to have identified the problem.
My apologies.  It does sound like the same issue, though.  What IS your
CHGTELNA  TIMMRKTIMO() set to?

I can tell you that by default on most platforms, telnet *client* does not
time out.  What platform are you using?  Can you give a better indication
of how long it is before the timeout occurs?  What messages are in QSYSOPR
message queue, and in your own joblog when the disconnect takes place?

It is also possible that the network (firewalls, gateways, routers) at your
location is tripping you up.  If you have a network administrator and any
of those devices, you might want to run this question by them.

If you're on linux, you can run tcpdump or other capture utility to see
what the activity between the client and the host is at the time of
disconnect.

HTH





Brendan Bispham <midrangel@black-and-blue.com>@midrange.com on 02/28/2002
08:30:21 AM

Please respond to linux5250@midrange.com

Sent by:  linux5250-admin@midrange.com


To:   linux5250@midrange.com
cc:
Subject:  Re: [LINUX5250] Timeouts


Thanks but I already looked (and offered an answer)... but the problem is
on
the PC... somehow the xt5250 windows closes after I press Enter but before
it
contacts the host... I can tell this because it's a connect-on-demand
connection and it didn't connect.


On Thursday 28 February 2002 13:19, Dennis Lovelady wrote:
> Hello, Brendan:
>
> Did you check the archives at http://archive.midrange.com/linux5250/ for
> this?  I think you'll find your answer there.
>
> Hint:  Search for (misspelled) "loosing connection"
>
> HTH
>
>
>
>
>
> Brendan Bispham <midrangel@black-and-blue.com>@midrange.com on 02/28/2002
> 07:20:49 AM
>
> Please respond to linux5250@midrange.com
>
> Sent by:  linux5250-admin@midrange.com
>
>
> To:   linux5250@midrange.com
> cc:
> Subject:  [LINUX5250] Timeouts
>
>
> On tn5250 0.17.1, mandrake 8.1...
>
> I'm xt5250'ing to a remote host and I've set the timeout values on the
> as400
> to v. high... the internet connection is connect-on-demand, and the idea
is
> to have a session that keeps alive even whilst the connection is down.
>
> It seems to work on the AS400 side, ie on reconnecting the session the
job
> resumes from where it left off.
>
> The problem is after a 10 minute wait (or so), the xt5250 session died
> without attempting to contact the host... ie it's not an AS400 system
value
> but a PC one.
>
> I cant find anything obvious in the sourcecode that says 'timeout=n' or
> something I can alter... What can I do to keep it alive?