|
Before I go thru to your recommendation, I need to know how many time the command uses by end users. ______________________________ Reply Separator _________________________________ Subject: Re: Monitoring command Author: MIDRANGE-L@midrange.com (AS400MAIL) at bngtw Date: 10/5/99 6:31 AM Couple years ago, the co I worked for had this issue. We ended up restricting people to only run queries in batch (unless they were IS personnel). If they don't voluntarily do it, there's a way to enforce it in either set-up or profiles (can't remember back that far). Another option that we looked into was forcing query to run in separate subsystem with lower priority so it didn't suck so much cpu and impact production. Bob ______________________________ Reply Separator _________________________________ Subject: Monitoring command Author: <MIDRANGE-L@midrange.com> at unix Date: 10/5/99 8:00 AM Queries takes a lot of I/O, I need to know how to monitor wrkqry and runqry command during working hours. Any idea? >> Transferred via Mail system of Information System & Technology Group << +--- | 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.