Timeout after inactivity

Discussion:

(too old to reply)

Garry

2003-08-11 10:17:00 UTC

Hi,
This problem has plagued me for a while...

When I log into my home AS/400 from work, it times out and I have to
re-login after just a few minutes of inactivity, if I do the same from
home, it does not time out even after an hour of leaving it. I'm using
V4R5 and using Mochasoft 5250 on Mac at work, and Solaris or HP-UX at
home.

Could a firewall or something be doing this? Are there different
TCP/IP settings for machines in or outside the local network?

Thanks

Garry

pete®

2003-08-11 13:03:28 UTC

Permalink

Hi,

I do not have the exact answer but I think it has something to do with the
QINACTITV system value. If set to *NONE I think the connection will hold.
But I am very interested in a permanent solution to this problem.

Thanks,
Peter

Post by Garry
Hi,
This problem has plagued me for a while...
When I log into my home AS/400 from work, it times out and I have to
re-login after just a few minutes of inactivity, if I do the same from
home, it does not time out even after an hour of leaving it. I'm using
V4R5 and using Mochasoft 5250 on Mac at work, and Solaris or HP-UX at
home.
Could a firewall or something be doing this? Are there different
TCP/IP settings for machines in or outside the local network?
Thanks
Garry

George Kinney

2003-08-12 03:40:02 UTC

Permalink

Its possible to setup a time-out notification (see QSYSINACTIV, or something
like
that :). I wrote a program a long time ago that services these messages,
and then takes
action based on user, terminal name, etc. The details are all a bit fuzzy
at the moment
though. Could someone have installed such a program on your machine?
(I seem to recall that TELNET, STRPASTHR and regular terminal connections
are
affected differently by this value, but I might be imagining it.)

Or more likely, is it the Mochasoft software? (Does it have an idle timeout
or such-like?)

e***@yahoo.com

2003-08-12 17:31:04 UTC

Permalink

CHGTELNA then F4 to prompt.

Their is a Timeout Value that we had to change to prevent our RF
scanners that use TELNET from timing-out. Default value is *CALC, we
use 7,200 seconds and it solved our problem.

pete®

2003-08-12 19:06:39 UTC

Permalink

The value 0 (zero) means there is no time-out. Should that not be used ?

Post by e***@yahoo.com
CHGTELNA then F4 to prompt.
Their is a Timeout Value that we had to change to prevent our RF
scanners that use TELNET from timing-out. Default value is *CALC, we
use 7,200 seconds and it solved our problem.

2003-08-18 15:27:26 UTC

Permalink

Thanks to everyone for the help, unfortunately my problem persists
though. I made a mistake in my original post, I'm using tn5250j, not
the Mochasoft product, but I don't suppose it makes much difference.
I'm not sure where to go from here, the fact that I have no problems
using it on the local network makes me think a Firewall is causing it.
The machine is in my home, and only I use it, so nobody could have
installed anything wierd or changed a setting except me.
Thanks again
Garry

I get timeouts like this using NS Elite. I also blame the firewall since the
timeouts happened as soon as it was installed ! However the firewall expert
cannot find any reasons. He claims the AS400 dosnt seem to ping the 5250
client in any logs so who knows.

--
Jonathan.