If you want to restrict long running queries you can do it by setting the query time limit. It can be done system wide by setting the QQRYTIMLMT or in an individual job by running CHGQRYA. Any time a user runs a query that is estimated to exceed this limit a message is sent indicating such, the response can be C to Cancel or I to Ignore and run the query anyway. You could set up a default reply for this message if desired. These parameters could help to restrict long running queries but don't help stop a large quantity of short running queries. > -----Original Message----- > From: Harry D. Angkasa [SMTP:firstname.lastname@example.org] > Sent: Monday, October 04, 1999 7:50 PM > To: MIDRANGE-L@midrange.com > Subject: Monitoring command > > > Queries takes a lot of I/O, I need to know how to monitor wrkqry and > runqry command during working hours. Any idea? > > > +--- | 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: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.