|
Simon, >but I know there is a bit in >the Work Control Block for a job that, if set, indicates the job has >exceeded the QINACTITV time. Would that help? Thanks, but I already have one of my programs working with the MI code Gene shared. In my case, it wouldn't have helped though -- part of what I'm wanting to look at is cases where QINACTITV time has not been reached. Users may have several sessios going for specific tasks, and want to be able to just toggle to that session on demand. Having a given session time-out while they are active in another is no good. But now I'll be able to do a more intelligent time-out. I can set the QINACTITV value back to a reasonable level, and have it trigger a program. That program can now check all sessions for the same user ID and determine if the user is still "active" at another session on the same physical device. If so, I'll want to let the inactive session stay alive. Only when all sessions have been idle too long will I want to take action. Doug
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.