Changes the impact setting for a running utility.
One of the following authorities:
ID = 2
Type = BACKUP
Database Name = IWZ
Partition Number = 1
Description = online db
Start Time = 07/19/2007 17:32:09.622395
State = Executing
Invocation Type = User
Throttling:
Priority = Unthrottled
Progress Monitoring:
Estimated Percentage Complete = 10
Total Work = 97867649689 bytes
Completed Work = 10124388481 bytes
The instance attachment must be made to partition 1 in
order to issue a SET UTIL_IMPACT_PRIORITY command
against the utility with ID 2. To do this, set DB2NODE=1 in the environment and then issue the instance attachment command. SET UTIL_IMPACT_PRIORITY FOR 2 TO 0
SET UTIL_IMPACT_PRIORITY FOR 3 TO 10
The database manager configuration parameter util_impact_lim sets the limit on the impact throttled utilities can have on the overall workload of the machine. 0-99 is a throttled percentage, 100 is no throttling.
The SET UTIL_IMPACT_PRIORITY command sets the priority that a particular utility has over the resources available to throttled utilities as defined by the util_impact_lim configuration parameter. (0 = unthrottled)
Both utilities combined should have no more than a 10% average impact on the total workload, and the utility with the higher priority will get more of the available workload resources. For both the backup and RUNSTATS operations, it is also possible to declare the impact priority within the command line of that utility. If you do not issue the SET UTIL_IMPACT_PRIORITY command, the utility will run unthrottled (irrespective of the setting of util_impact_lim).
To view the current priority setting for the utilities that are running, you can use the LIST UTILITIES command.
Throttling requires having an impact policy defined by setting the util_impact_lim configuration parameter.