9.6.10: Service Pack 1

This topic contains information about fixes and updates in this service pack.

For information about issues corrected in this service pack, see Known and corrected issues.

What's new

Instance to device mapping 

When PATROL Agent is reporting data in TrueSight Infrastructure Management, the DB2 nodes are shown as devices on the TrueSight Infrastructure Management UI. This is called "instance to device mapping". This feature has been introduced in 9.6.10 release of BMC PATROL for DB2. 

In some cases, you might want to disable this feature to display all instances and parameters of the KM under the device in the Configured Patrol Agent. To disable "instance to device mapping" for a given installation of PATROL Agent and KM, you must apply the following PCM rule: /PSO/DB2/<<environment name>>/BPPMI2D " = { REPLACE = "false" },

Introduced new pconfig variables

The following PATROL configuration variables have been added to enhance the current KM functionality.

PATROL configuration variableDescription
/PSO/DB2/<<environment name>>/isPConfigDestroyTree(Optional) Set this variable to 1 or true if you want to destroy the DB2 environment and rebuild it from the beginning

Note: Use this variable when you want to delete pconfig variable like filters, shutdown path and other variables.

/PSO/DB2/<<environment name>>/disableRemoteDBMonitoring

 (Optional) Set this variable to 1 or true if you do not want to discover remote databases.
/PSO/DB2/<<environment name>>/<<instance name>>/shutdownInstanceFilePath

Every 1 minute, the KM checks if the file registered in this pconfig variable exists or not.

If the file exist,

  • The km will shutdown a specific DB2 instance instance name that appears in the pconfig variable path
  • This specific DB2 instance will be discovered as expected

Note: The shutdown file must be located on the DB2 machine.


(Optional) Every 30 seconds, the KM checks if the file registered in this pconfig variable exists or not.

  • If the file exists, the KM will shutdown and destroy all the environments below the DB2 icon in the console. 
  • If the file does not exist, the KM will discover the environments.

Note: The shutdown file must be located on the PATROL Agent machine.


(Optional) Set the timeout needed to read from the channels in seconds.

Note: Restart the PATROL Agent to apply these changes.
BMC recommends that you do not modify this variable without assistance from BMC customer support.

What's changed

Hash mapping disabled for instance names

With this release, hash mapping for instance names has been disabled by default. The value of InstanceConversionMapping property is set to false in the <patrol home>/Patrol3/pso/conf/pso.properties configuration file to disable hash mapping. This will disable hash mapping for instance names in all the configured environments. With this enhancement, the complete path of the parameters is displayed on the PATROL Consoles. Hash mapping can be enabled for specific environments by using the JVM arguments.  

Upgrade impact

Consider the following points to retain the environment history and to ensure smooth upgrade from version 9.6.00 to version 9.6.10 of BMC PATROL for DB2:

If you want to use hash code paths in the instance names, BMC recommends that you, as a database administrator, add -DlongInstanceMapping=false JVM argument to the respective environment. To add -DLongInstanceMapping=false JVM argument,

  • Right click the Environment name >  KM commands > KM Administration > Define JVM Arguments. Enter the argument. 


  • Set the value to the /PSO/DB2/<<environment name>>/jvmArgs pconfig variable.
Was this page helpful? Yes No Submitting... Thank you