Re: Analyzing user interactive session length

The only thought that comes to mind would be to set the timer lower but use a message queue instead of ending or suspending the job. Then a program reads that queue and saves the data. What I can't recall is if the messages repeat if the user still does nothing or if you get only one.

But here is what we used to do. Again use the message queue because that is the key to flexibility. It all started 'when the paint was white' because *I* got tired of signing back on to a session I had 'neglected' for a while during the day. Back then I was often in SEU so...

So I wrote a program to read that queue. We settled on QINACTMON for the name. First thing it does is check the time. We determined that our main business hours were 7A to 6P and so during those hours the inactivity timer was set rather high. When the clock ticked past 6 the program changed the timeout down to 1 hour. After 8PM when nightly batch began we lowered it more to 15 min. Just before the backup I think we went even lower and after the backup raised it again to 1 hour and up to the longest duration at 7AM. The program easily handles this by using a time out the rcvmsg and checking the clock. Oh how nice a case statement would have been 30 years ago. :-) Additionally (because *I* wrote the program) it never disconnected or ended any of MY sessions in my office. I didn't use the app and wouldn't have any locks. After 6PM though my sessions were also fair game.

Point here though is you don't need ONE inactivity time to fit all, leverage a simple program to use different duration for different parts of the day.

FURTHER you can copbine QDSCJOBITV with this logic. For example we disconnect users HR rather rapidly but let the QDSCJOBITV counter remain high during the day. Lower this at night as well.

- DrF

On 3/24/2021 7:25 PM, 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
Direct: 330.487.3739 | Cell: 330.888.8085 | Toll Free: 800.225.7712
2450 Edison Blvd, Suite 3, Twinsburg OH 44087
hc-companies.com<https://www.hc-companies.com/>
Leader in Horticultural Containers
[cid:image003.png@01D720E3.1C02F5A0]<https://www.linkedin.com/company/the-hc-companies> [cid:image004.png@01D720E3.1C02F5A0] <https://www.facebook.com/HCCompanies/> [cid:image005.png@01D720E3.1C02F5A0] <https://www.instagram.com/hccompanies/> [cid:image006.png@01D720E3.1C02F5A0] <https://twitter.com/hc_companies>

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.