400 keeps signing me off

[Kevin Buckley]

We have a new 400 and it signs us off after 3-4 minutes of inactivity.

The message in the job log is : "The request shutdown was caused by either
the user turning the power off, by a device error, or the ASCII controller
inactivity timer expired."

I have looked and looked for that inactivity timer value, to no avail.

Any suggestions?

[John]

Hi Kevin
Check the system value QINACTITV and change it to *NONE
Regards
John

Kevin Buckley wrote in message <3737...@199.186.16.51>...

[Kevin Buckley]

It was set to *None. I changed it to 100 and back to *none, with no effect
on my problem.

Any other guesses, anyone?

-kb
John wrote in message <7h8jim$6rj$1...@hermes.is.co.za>...

[Frank Healy]

Hi Kevin,

What devices and connection/protocol media are you experiencing this
problem on?

Frank

[Olaf Brodtmann]

Hi Kevin,

which AS400 Release are you using? Do you use Client Access and IP ?

Try first to check the SYSVAL for QINACTIV (inactivity timer)

If you are using CA, you could try with automatic reconnect in the 5250
session configuration.

Good luck,
Olaf

Kevin Buckley <kevin_...@compuware.com.com> schrieb in im Newsbeitrag:
3737...@199.186.16.51...

[Gunnar Eriksson]

To understand and come closer to a solution it is necessery to know
in witch way you are communicating with the AS400. TCP/IP,AnyNet,SNA ore
Twinax.

Gunnar Eriksson

Kevin Buckley wrote in message <3737...@199.186.16.51>...

[jen...@my-dejanews.com]

Kevin, do you have the same symptoms like described below. If yes, please
keep in touch with me. --- Anynet 17, Keepalive, Performance, Winsock We
have the same symptoms like APAR # SA67482: It takes over two minutes to
establish a connection. After the keeplive timer-time (default 3 minutes) and
no user entry the session drops with error "Anynet-17" (anynet send 5
keeplaive to host, no host response), sometimes it drops with error
"Anynet-19" (receive returns zero... socket closed) The cause of the above
APAR was on the host side. But this problem seems to be on the client: some
clients don´t have this problem, some other do. We found this problem with
Win95, Win98 and Win NT. First we used a circumvention to set the keepalive
timer to 999 minutes and used the AS/400 Patch SF52788 to set the keepalive
timer in the AS/400, the connections don´t drop but the establishing of the
connection still takes over two minutes. After a lot of tracing and trouble
shooting we found the cause of the problem in the client side: !!! At the
Win PCs with the Problem there are more than one network bindings with
different IP-Adresses !!! For example: TCP/IP -> Remote Network has IP
Adress 192.168.10.1 TCP/IP -> Local Network has IP Adress 192.168.10.2 When
the Client closes a connection it seems it closes with another IP-Adress. We
found that host and client had different socket numbers for Port 397 and idle
in the state Close_Wait for about two minutes. In this time Client Access
waits and waits and waits... for this port to close. This seems to be a
Winsock Problem, has anyone any hint how to solve this? Jens --- In article
<3737...@199.186.16.51>, "Kevin Buckley" <kevin_...@compuware.com.com>
wrote: > We have a new 400 and it signs us off after 3-4 minutes of

inactivity. > > The message in the job log is : "The request shutdown was
caused by either > the user turning the power off, by a device error, or the
ASCII controller > inactivity timer expired." > > I have looked and looked
for that inactivity timer value, to no avail. > > Any suggestions? > >

--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---

[Paul Wellman]

I have seen this problem occur when power management is turned on the PC.
Try disabling power management and see if that makes a difference.
Paul
Gunnar Eriksson wrote in message <7hb4o2$g...@newsfeed.enator.net>...

>To understand and come closer to a solution it is necessery to know
>in witch way you are communicating with the AS400. TCP/IP,AnyNet,SNA ore
>Twinax.
>
>
>Gunnar Eriksson
>
>Kevin Buckley wrote in message <3737...@199.186.16.51>...

[Kevin Buckley]

Frank - I've experienced it both on PCs using Client Access and other
terminals telnetting in, using TCP/IP.

-Kevin.

Frank Healy wrote in message <3738C5...@encorecsi.com>...

>Hi Kevin,
>
>What devices and connection/protocol media are you experiencing this
>problem on?
>
>Frank
>
>Kevin Buckley wrote:
>>
>> It was set to *None. I changed it to 100 and back to *none, with no
effect
>> on my problem.
>>
>> Any other guesses, anyone?
>>
>> -kb
>> John wrote in message <7h8jim$6rj$1...@hermes.is.co.za>...
>> >Hi Kevin
>> >Check the system value QINACTITV and change it to *NONE
>> >Regards
>> >John
>> >
>> >

[Kevin Buckley]

TCP/IP.

Gunnar Eriksson wrote in message <7hb4o2$g...@newsfeed.enator.net>...
>To understand and come closer to a solution it is necessery to know
>in witch way you are communicating with the AS400. TCP/IP,AnyNet,SNA ore
>Twinax.
>
>
>Gunnar Eriksson
>

[Kevin Buckley]

V4R3. And yes, I have seen it happen during a Client Access over IP session.
But it's also happened when telnetting from one 400 to this one.

It's some sort of inactivity timer. If you hit enter, or a function key
every so often, it won't bump you off.

And no, QINACTIV isn't it. And yes, I've checked the Auto-reconnect box in
Client Access, but all that does is give a sign-on screen as soon as the 400
has booted me off.

ARGH!!!!

-kb

Olaf Brodtmann wrote in message <37388...@news.ka.choin.net>...

>Hi Kevin,
>
>which AS400 Release are you using? Do you use Client Access and IP ?
>
>Try first to check the SYSVAL for QINACTIV (inactivity timer)
>
>If you are using CA, you could try with automatic reconnect in the 5250
>session configuration.
>
>Good luck,
>Olaf
>
>Kevin Buckley <kevin_...@compuware.com.com> schrieb in im Newsbeitrag:
>3737...@199.186.16.51...

[Thomas]

Kevin:

Since no one has asked yet... what is your TELNET inactivity timeout set
for? Prompt the CHGTELNA command to see the current value and perheps
raise it. You might want to set it a little higher than the QINACTITV
system value.

Tom Liotta

In article <3737...@199.186.16.51>,
"Kevin Buckley" <kevin_...@compuware.com.com> wrote:

> We have a new 400 and it signs us off after 3-4 minutes of inactivity.
>
> The message in the job log is : "The request shutdown was caused by
either
> the user turning the power off, by a device error, or the ASCII
controller
> inactivity timer expired."
>
> I have looked and looked for that inactivity timer value, to no avail.
>
> Any suggestions?
>
>

--
Tom Liotta
AS/400 systems programmer

[Kevin Buckley]

That just might be it! I changed that value, but I think I need to end the
telnet server and restart before it will take effect. Can't do that during
work hours!

Thanks, Tom.

Thomas wrote in message <7hdbtd$b3b$1...@nnrp1.deja.com>...

[Frank Healy]

Kevin:

In addition to the SYSVAL QINACTITV, the CHGTELNA command has a timeout
function called INACTTIMO. What doesn't make sense though is the
default paramter is 0, which says don't timeout. I wonder if someone
has changed this command over the course of time. I believe you have to
do an ENDTCPSVR (*TELNET)- STRTCPSVR (*TELNET) to make any change
active.

Best regards,

Frank

Kevin Buckley wrote:
>
> Frank - I've experienced it both on PCs using Client Access and other
> terminals telnetting in, using TCP/IP.
>
> -Kevin.
>
> Frank Healy wrote in message <3738C5...@encorecsi.com>...
> >Hi Kevin,
> >
> >What devices and connection/protocol media are you experiencing this
> >problem on?
> >
> >Frank
> >
> >Kevin Buckley wrote:
> >>
> >> It was set to *None. I changed it to 100 and back to *none, with no
> effect
> >> on my problem.
> >>
> >> Any other guesses, anyone?
> >>
> >> -kb
> >> John wrote in message <7h8jim$6rj$1...@hermes.is.co.za>...
> >> >Hi Kevin
> >> >Check the system value QINACTITV and change it to *NONE
> >> >Regards
> >> >John
> >> >
> >> >

> >> >Kevin Buckley wrote in message <3737...@199.186.16.51>...