You can modify different types of attributes of the queries that you will execute during a certain job with the CHGQRYA command. The types of attributes that you can modify include:
Before the system starts a query, the system checks the query time limit against the estimated elapsed query time. The system also uses a time limit of zero to optimize performance on queries without having to run through several iterations.
You can check the inquiry message CPA4259 for the predicted runtime and for what operations the query will perform. If the query is cancelled, debug messages will still be written to the joblog.
The DB2 UDB for AS/400 Predictive Query Governor can stop the initiation of a query if the query's estimated or predicted runtime (elapsed execution time) is excessive. The governor acts before a query is run instead of while a query is run. You can use it in any interactive or batch job on AS/400. You can also use it with all DB2 UDB for AS/400 query interfaces; it is not limited to use with SQL queries. See Control long-running queries with the DB2 UDB for AS/400 Predictive Query Governor for details.