Setting submitter resource limits

You can specify whether or not you want a submitter's queries to be intercepted by Query Patroller. If you specify that they will be intercepted, you can also limit the resources that are used by a submitter, so that the submitter cannot use too many of the system's resources.

• To limit submitter resources using the Query Patroller Center method
  1. Open the Submitter Properties notebook:
     1. From the Query Patroller Center, expand the object tree under the User Administration folder to find the Submitters folder.
     2. Click the Submitters folder. Any existing submitters are displayed in the pane on the right side of the window (the contents pane).
     3. Right-click the submitter that you want to modify in the contents pane, and click Properties in the pop-up menu. The Submitter Properties notebook opens.
     Note: You can also open the Submitter Properties window by double-clicking the submitter profile that you want to change.
  2. Click the Resources tab.
  3. If you do not want Query Patroller to intercept queries from the submitter you are creating, select the Do not intercept queries from this submitter check box. Query Patroller will neither perform cost evaluation nor create a query in the historical analysis view. Query Patroller will not manage queries submitted by submitters with this profile.
  4. In the Minimum cost to manage field, type a number greater than or equal to 0 and less than the Maximum cost of a query value. Queries costing less than this value will not be managed by Query Patroller.
  5. In the Maximum number of queries field, type the maximum number of queries that this submitter is permitted to run simultaneously. Additional queries will be queued. To allow an unlimited number of queries, to run simultaneously, leave the field blank.
  6. In the Maximum cost of a query field, type a number for the maximum query cost. If the submitter submits a query with an estimated cost that is higher than this value, the query is held. To set the value to unlimited, leave the field blank.
  7. In the Maximum size of a result table field, type a value for the maximum number of result rows to be stored in a result table. If you leave the field blank, DB2® will always make this submitter's result table large enough to accommodate the entire result set.
  8. In the Queue priority field, type a value from 0 to 999 to represent the priority assigned to a query when a query is submitted. Higher numbers indicate higher priority.
  9. Click OK to update the submitter profile.
• To limit submitter resources using the Command line method:
  1. Issue theUPDATE SUBMITTER_PROFILE command using the following parameters: