|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Is the timeout happening on the AS/400 or the client? I know that when utilizing pass through queries from MS Access and the like, the client side software sets its own timeout values, which may or may not be changeable. (It is with Access, but defaults to 30 or 60 seconds) Typically I only run into queries that want to puke like this if they are just too complex or don't make good use of existing indexes. (or are joined with data not visible to the 400, such as local tables and queries, which is a big performance killing no-no.) >I have a software vendor developing an application that utilizes an ODBC >request (which he describes as a passthru, not a stored procedure) and is >incurring timeout errors (SQL0666). I have the system value for my >QQRYTIMLMT set to *NOMAX. Any suggestions on how to fix this? It appears >that the query request is almost causing itself to default to 30 seconds >instead of *nomax.
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.
midrange.com
