Re: MS Access 97 and CA ODBC - Query Timeout -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Alexei,

Technically, you are correct.  But, your answer does not apply to my 
predicament.
QQRYTIMLMT is set to *nomax.  The CHGQYRA is happening "on it's own" inside an 
Access
ODBC query.

Bill

> On AS/400 there's a feature, called query governor. It's purpose in life
> is exactly this - limiting the duration of queries. It will not allow
> query to run, if estimated runtime is above set limit.
> Limit is controlled by QQRYTIMLMT system value - system-wide - or
> CHGQRYA command - job specific.
> If you have 60 seconds default and query is going to take longer - then
> it would explain what you see.
>

+---
| 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
+---

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.