|
You could also check out this TAA Tool: http://www.taatool.com/document/L_chkinact.htm Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Jeffry Kennedy <jkennedy@xxxxxxxxxx To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> com> cc: Sent by: Subject: Re: Best solutions for Users who don't logoff midrange-l-bounces@x idrange.com 04/26/2003 12:38 PM Please respond to Midrange Systems Technical Discussion We use ROBOT Scheduler to run a 'supplied' job to force idle users and a specific time, it check's for number of minutes idle and then logs off the user. I had the same problem with file locks. Vern Hamberg wrote: > There are system values for workstation inactivity--QINACTITV & QINACTMSGQ. > You could set the former to 15 minutes, then get a CPI1126 message in a > message you name in the latter. ROBOT/Console or Messenger-Plus or ??? or > your own program could monitor that queue and do whaterver you want. > > Also on point, we have a product called lock/DETECTOR that will tell you > what jobs are waiting for a lock and what jobs are holding those locks, > either as an ongoing monitor or as you run the command. > > End of commercial in direct response to a question! > > HTH > > Vern > > At 02:40 PM 4/25/2003 -0700, you wrote: > >Hi I am looking at a situation at a company where because someone doesn't > >logoff and they have an open file, an update program doesn't work. They > >also create many sessions and this causes performance degradation. I was > >thinking that there could be a way to check and see if a user hasn't been > >doing anything for over 15 minutes, like hitting the keyboard. Then I > >would want to alert the senior staff to contact this person and get them > >to sign off. I suppose you could have them emailed and even phoned. Does > >this make sense?Thanks,Rob > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.