RE: MS Access 97 and CA ODBC - Query Timeout

["Pytel, Alexei" <pytela1@xxxxxxxxxxxxxxxx>]

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.



    Best regards,

          Alexei Pytel



> -----Original Message-----
> From: Bill Robins [SMTP:brobins@ix.netcom.com]
> Sent: Friday, October 16, 1998 1:46 PM
> To:   Midrange Discussion List
> Subject:      MS Access 97 and CA ODBC - Query Timeout
> 
> Ran into something interesting that seems to apply only to Access
> (97).  I am running
> under CA/Win95 V3.1.2 and submitting a query that times out on the 400
> side.  The
> QZDAINIT won't run the query because the estimated time of execution
> is 193 seconds
> and "something" limited the query to 60 seconds.  The message id is
> CPF427F, which
> points to a CHGQRYA being run.
> 
> Since I don't/haven't had this problem with many other packages, what
> is going on
> here?  I can find no parameter to change.
> 
> Bill
> 
> +---
> | 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 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
+---