× 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: Re: MS Access 97 and CA ODBC - Query Timeout
  • From: bclark@xxxxxxxxxxxx (Bob Clark)
  • Date: Mon, 19 Oct 1998 07:32:06 -0500
  • Organization: US Safety

We have noticed the same problem recently.  I just checked the system value
previously mentioned and it is set for *NOMAX.

"Pytel, Alexei" wrote:

> 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
> +---
begin:vcard
n:Clark;Bob
x-mozilla-html:FALSE
org:US Safety
adr:;;;Lenexa;Ks;66214;USA
version:2.1
email;internet:bclark@ussafety.com
title:Programmer/Analyst
tel;fax:913-599-1703
tel;work:913-599-5555 x274
x-mozilla-cpt:;0
fn:Bob Clark
end:vcard


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.