× 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.


  • Subject: How to change query time limit for SQL requests via ODBC?
  • From: George Hughen <ghughen@xxxxxxxxxx>
  • Date: Thu, 4 Sep 1997 19:00:01 -0700

Greetings all:

I am trying to find out how to overcome a problem that I am having when
trying to run a certain SQL statement from a VB program via ODBC.
I get the error message: SQL0666, which reads: 
        Estimated query processing time 31 exceeds limit 30.

        (This also occurs in the job log of the QZDASOINIT job as CPF427F)

This indicates that the server job somehow changes its time limit to 
30 seconds using the CHGQRYA CL command (or possibly by some
other method).

Incidentally, the query only takes 1 second when run using interactive SQL.
So much for the predictive query governor!

I have had a little luck by changing the job description that the server
job uses to INQMSGRPY(*SYSRPYL) and putting a reply
of 'I' (ignore) in the System Reply list entries for CPA4259, but
I wonder if there is a better way to do this?

Thanks,
George Hughen
Transition Systems, Inc.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.