DB2 graphic QMF Version 8

Resource group common controls

The following common controls pertain to an entire resource group:

Description
Although this field is not a control (no actions are taken due to the value supplied), it allows you to record a description about this resource group. The maximum length is 40 characters.
Activate Resource Group?
This flag controls whether or not this entire resource group is active. Its value must be Y (to activate or enable) or N (to deactivate or disable). When a resource group is disabled, all control schedules are disabled. When a resource group is enabled, only the control schedules that are active are enabled.
Log Resource Violations?
This flag controls the logging that Governor will perform when a resource violation occurs. If it is set to Q, a message will be logged to the user's DSQDEBUG data set. If it is set to R, a message will be logged to the user's RAADEBUG data set. If it is set to B, messages will be logged to both data sets. If it is set to N, no messages will be logged.
Asynchronous Timer Interval
There are some scheduled controls that are governed asynchronously. Specifically, CPU and row limits are governed at distinct intervals while QMF is processing commands. The interval at which these controls are checked is specified by this option (in wall-clock seconds). If this value is 0, asynchronous governing is disabled. (CPU time limits are only checked asynchronously, so a value of 0 in this field effectively disables CPU time limit checking.)
REXX Program Name
If you are not using Query Analyzer, this field is ignored. If you are using Query Analyzer, then you can specify the name of an exit routine that Query Analyzer should invoke. If you leave this field blank, then it will default to the sample exit routine named RAARXQA. If you have written your own exit routine, specify the name here. See "Sample exit routine" for a more detailed discussion.
Plan Table Owner/Current SQLID
If you are not using Query Analyzer, this field is ignored. If you are using Query Analyzer, then you can specify the CURRENT SQLID that Query Analyzer should use during query analysis.

The value that you enter here will have two effects:

Before setting this value, review the restrictions for setting CURRENT SQLID in DB2 Administration Guide.

Create Plan Table In Database
If you are not using Query Analyzer, this field is ignored. Otherwise, you can specify the database in which Query Analyzer should create a PLAN_TABLE for a user if one does not already exist. If you leave this field blank and a PLAN_TABLE does not exist, query analysis will be bypassed.
Create Plan Table In Table Space
If you are not using Query Analyzer, this field is ignored. Otherwise, you can specify the table space in which Query Analyzer should create a PLAN_TABLE for a user if one does not exist. You cannot enter a value in this field unless you also enter a value in the Create Plan In Database field.
DB2 Subsystem ID for *
This field is used by the HPO/Governor module under CICS and can be ignored if you are not planning to govern or track activity under QMF/CICS. Otherwise, if the location field is non-blank, then you need to fill in the name of the DB2 subsystem ID that correlates to this location. If the location field is blank, the subsystem ID of the current DB2 will be used internally, but may be explicitly specified here as well.


Go to the previous page Go to the next page

Downloads | Library | Support | Support Policy | Terms of use | Feedback
Copyright IBM Corporation 1982,2004 Copyright IBM Corporation 1982, 2004
timestamp Last updated: March, 2004