|
Hi Michael, Thanks for your answer, but I don't think this would solve my problem. According to your mail, this QQRYTIMLMT only decides if the query is to start or not. And when it is started, it still consumes the same amount of CPU. I do want to let the query run, but with less CPU. Johan Vangilbergen YUSE Phone : +32 16 74 50 80 Fax : +32 16 74 50 89 Email : jvg@xxxxxxx Web : WWW.Yuse.be Address : Bondgenotenlaan 138, B-3000 Leuven, Belgium -----Original Message----- From: midrange-l-bounces+jvg=yuse.be@xxxxxxxxxxxx [mailto:midrange-l-bounces+jvg=yuse.be@xxxxxxxxxxxx] On Behalf Of Michael Ryan Sent: dinsdag 13 februari 2007 16:58 To: Midrange Systems Technical Discussion Subject: Re: Query using (too) much CPU Try system value QQRYTIMLMT : QQRYTIMLMT Database query time limit. The limit that is compared to the estimated number of elapsed seconds that a query requires to run in order to determine if a database query is allowed to start. NOTE: You must have *ALLOBJ and *SECADM special authorities to change this system value. A change to the shipped value takes effect immediately. The shipped value is *NOMAX. The possible values for the QQRYTIMLMT system value are: o *NOMAX: There is no maximum number of estimated elapsed seconds. o 0 - 2147352578: Specifies a number of seconds which is compared to the estimated number of elapsed seconds required to run a query. If the estimated elapsed seconds is greater than this value, the query is not started.
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.