Skip to Content

Using the ConfigUpdates parameter

The ConfigUpdates parameter checks for changes to the configuration variables. It does this by checking for the /DB2Config/KMConfigUpdated variable. When a change is detected, this parameter creates an annotation. Setting this variable is only required if changes are made to the "indoubt," "TbspIOMon," or "perf-Monitor" settings. Otherwise, changes to the pconfig variables are picked up in the collection process or affected discovery. If the update is applied to the instance successfully, the ConfigUpdates parameter is set to 1 and creates and annotation indicating that the /DB2Config/ KMConfigUpdated variable was detected.

Error
Warning

No validations are performed on the new configuration variables and parameter property changes. You must verify that the changes perform correctly on each instance where they were applied.

Before a variable change can take effect, the following events must occur:

  1. Discovery or the appropriate parameters complete the next cycle.
  2. The ConfigUpdates parameter runs and discovers the new configuration variable.
  3. The appropriate parameter completes another cycle after ConfigUpdates discovers the new variable or discovery occurs. (Discovery is only required if changes to "indoubt," "TbspIOMon," or "perf-Monitor" are made.)
  4. If applicable, the appropriate collector parameter updates the effected consumer parameters.

For information about parameter poll times and dependencies see Parameters.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for DB2 Universal Database 9.0