In more recent OS/400 versions, QQRYTIMLMT is set to *NOMAX by default, but it could have been previously set to a lower value. OS/400’s query time limit is kept in the Query processing time limit system value, QQRYTIMLMT, which can be viewed or changed through the following Work with System Values command (WRKSYSVAL): Where xxx and yyy represent the estimated amount of time it will take to process the query and the OS/400 query time limit, respectively. Estimated query processing time xxx exceeds limit yyy. ![]() When it is determined that the query will process longer than OS/400’s query timeout limit, the query goes belly up and returns something similar to the following error message: While others have documented how to avoid this error by changing an ADO property, newer iSeries Access ODBC drivers allow you to disable query timeouts directly within your Data Sources (DSN).įor those who have not run into it, the SQL0666 error usually happens when you are using ODBC to process a large query from your PC. ![]() One of the strangest is the SQL0666 error, which stops SQL query processing when the estimated query run time exceeds the system’s query processing limit. ![]() OS/400 ODBC processing is notorious for obscure error messages that offer little information about their causes or their solutions. Admin Alert: Turning Off ODBC Query Timeout Limits
0 Comments
Leave a Reply. |