Re: Analyzing user interactive session length

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

We don't care how long a session sits idle... our solution was driven 
by a balance between user and auditor complaints--  users aiming for 
longer, auditors for shorter!

QINACTITV = 90 minutes
QINACTMSGQ = *DSCJOB
QDSCJOBITV = 60

What this gives us:  After 90 minutes of inactivity a user's job is 
returned to a signon screen (but is still 'active').
After another 60 minutes the job is ended.

If a user's screen drops back to the signon screen, they have an 
additional 60 minutes to sign on and pick up where they left off. 
That's 2-1/2 hours-- long enough for a long meeting or a leisurely 
lunch!

--Paul E Musselman

.

At 11:25 PM +0000 3/24/21, Howie, Bill wrote:
> Hello all,
>
> In my shop we are looking at changing the length of time that we 
> leave sessions connected with no activity before we have the 
> QINACTITV system value end the session.  My boss has asked me if we 
> have a way to know the average length of time that a session will 
> sit idle.  Right now our system value is set at 5 hours, which 
> sometimes allows some off-hours locking issues to occur when the 
> "problem" session has been sitting idle for several hours, but 
> hasn't met the 5-hour limit yet, and a currently-working interactive 
> user tries to access a record that the inactive user has locked.
>
> Have any of you tried to analyze average idle time?  We're basically 
> trying to figure out how much we can shorten this time without 
> ticking off the user community.  Any thoughts on this would be most 
> appreciated.  Thanks!
>
> [Related image]<https://www.hc-companies.com/>Bill Howie
> Senior ERP Programmer/Analyst