DB2 Version 9.7 for Linux, UNIX, and Windows

Aggregate registry variables

Use an aggregate registry variable to group several registry variables as a configuration that is identified by another registry variable name. Each registry variable that is part of the group has a predefined setting. The aggregate registry variable is given a value that is interpreted as declaring several registry variables.

The intention of an aggregate registry variable is to ease registry configuration for broad operational objectives.

The only valid aggregate registry variable is DB2_WORKLOAD.

Any registry variable that is implicitly configured through an aggregate registry variable might also be explicitly defined. Explicitly setting a registry variable that was previously given a value through the use of an aggregate registry variable is useful when doing performance or diagnostic testing. Explicitly setting a variable that is configured implicitly by an aggregate is referred to as overriding the variable.

If you attempt to modify an explicitly set registry variable by using an aggregate registry variable, a warning is issued and the explicitly set value is kept. This warning tells you that the explicit value is maintained. If the aggregate registry variable is used first and then you specify an explicit registry variable, a warning is not given.

When you query the aggregate registry variable, only the value assigned to that variable is shown. Most users should not care about the values for each individual variable.

The following example shows the interaction between using the aggregate registry variable and explicitly setting a registry variable. To control your database environment, you might set the DB2_WORKLOAD aggregate registry variable to SAP and override the DB2_SKIPDELETED registry variable to NO. By running the db2set command, you receive the following results:

   DB2_WORKLOAD=SAP
   DB2_SKIPDELETED=NO

In another situation, you might set DB2ENVLIST, set the DB2_WORKLOAD aggregate registry variable to SAP, and override the DB2_SKIPDELETED registry variable to NO. When you issue the db2set command, the registry variables that were configured automatically by setting the aggregate registry variable show the name of the aggregate displayed in square brackets, next to its value. The DB2_SKIPDELETED registry variable shows a NO value, with [O] displayed next to its value.

When you no longer require the configuration that is associated with DB2_WORKLOAD, delete the implicit values of each registry variable in the group by deleting the value of the aggregate registry variable. Use the following command to delete the value of the DB2_WORKLOAD variable:

db2set DB2_WORKLOAD=

After deleting the DB2_WORKLOAD aggregate registry variable value, restart the database. After the database is restarted, the registry variables that were implicitly configured by the aggregate registry variable are no longer in effect.

Deleting the value of an aggregate registry variable does not delete the value for a registry variable that was set explicitly. It does not matter that the registry variable is a member of the group definition that was deleted. The explicit setting for the registry variable is maintained.

You might need to see the values for each registry variable that is a member of the DB2_WORKLOAD aggregate registry variable. For instance, you might want to see the values that would be used if you configured DB2_WORKLOAD to SAP. To find the values that would be used if DB2_WORKLOAD=SAP, run db2set -gd DB2_WORKLOAD=SAP.