|
Hello Scott, Thanks for the reply. We had already tried this option. This works fine for batch jobs but for interactive jobs, it just acts weirdly. We had set the limit to 30 min, but the interactive query continued till 45 min. Following are other options we tried: 1. Doing ENDJOb - But it ends the session (and it should cause it's the same job) 2. ENDRSQ - But it's not job wise, it kills the job from which it's submitted.(Is there a way to do this job wise?) Therefore, I wanted to know if there is any way we could end ANY command that is running interactively on some user's session.(without of course the users intervention). I'm thinking of trying out capturing user's session through IGC files, but not so sure how to implement it. Or, is there any MI function than could do it. We have got very less time to implement it, don't know where to proceed. Thanks, Rajeev. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.