When the maximum processor time is exceeded

When a query exceeds the maximum processor time, the DB2 governor ends the query and returns an SQL error code of -905. QMF then knows that the governor canceled the query. How QMF treats this information depends on where in a QMF session the governor canceled the query:

During QMF Initialization

When it begins a user's session, QMF runs several queries that the DB2 governor monitors. If any of these queries are canceled, QMF ends the session. Before the session ends, QMF writes an explanatory record in the user's DSQDEBUG data set.

The session end might occur during periods when QMF sessions are not allowed. To enforce this restriction, people who attempt to use QMF during such a period of time might be assigned a maximum processor time of zero. This causes the cancellation of any monitored query.

After QMF Initialization

After initialization, QMF treats the cancellation of a query just as it treats any other error in running the query. Suppose, for example, that the governor cancels an INSERT query for which the user issued a RUN command. Then the inserts, if any, are undone, and the query panel is displayed with an error message. If the user then asks for message help, a panel explaining the governor's action is displayed.

Suppose instead that a cancellation takes effect while the user is scrolling through a report. Then it is likely that a row fetch caused the cancellation. The cancellation leaves the DATA object incomplete. Because DB2 closes the cursor, the DATA object cannot be completed.