Differences between governors

You can supplement the operations of the QMF governor with the DB2 governor. Before you do, you should know how the governors differ.

• The DB2 governor limits its monitoring to the types of queries mentioned in the previous section. It does not monitor, for example, the processor time spent in running a CREATE or DROP query.
• The DB2 governor limits its monitoring to processor time. It does not count row fetches, as the QMF governor does.
• Processor time for the DB2 governor includes only the time consumed by DB2. In contrast, the QMF governor includes the time QMF spends running a command--manipulating a spill file, for example, or displaying the first page of the results of running a SELECT query.
• When a user runs a SELECT query, the DB2 governor monitors all the time DB2 spends running the query, beginning with the PREPARE statement and continuing through the row fetches and the closing of the cursor. The QMF governor ends its monitoring after the first page of the results are displayed. Any subsequent row fetch is treated as part of the scrolling command that caused the fetch to occur.
• The DB2 governor makes no provision for a cancellation prompt; its only control parameter for a given QMF session is maximum processor time.