Tablespace custom health (TblspCustomHealth)

This parameter is used to handle following Pconfig:

For JDBC monitoring it uses the following rulesets:
"/PSO/DB2/JDBC/<<environment name>>/BMC_FORCE/<<DB2 database name>>/tableSpaces/stateWarnList" = {
REPLACE = "<<optional - This is relevant to JDBC monitoring only. This variable contains a list of tablespace states values in hexadecimal separated by comma, so the TblspCustomHealth parameter of any tablespace which is associated to a specific database will be in warning state if its value exists in the list defined by the users for this pconfig variable. The hex values are integer values you can add the prefix '0x' for any value. For example for the stateWarnList, you can use '2,0x8,0xc'.>>"

},
"/PSO/DB2/JDBC/<<environment name>>/BMC_FORCE/<<DB2 database name>>/tableSpaces/stateAlertList" = {
REPLACE = "<<optional - This is relevant to JDBC monitoring only. This variable contains a list of tablespace states values in hexadecimal separated by comma, so the TblspCustomHealth parameter of any tablespace which is associated to a specific database will be in alarm state if its value exists in the list defined by the users for this pconfig variable. The hex values are integer values you can add the prefix '0x' for any value. For example for the stateAlertList, you can use '2,0x8,0xc'.>>"
},

For Local/RemoteUnix/RemoteWin the following Pconfig is used:

"/PSO/DB2/<<DB type>>/<<environment name>>/BMC_FORCE/<<DB2 instance name>>/tableSpaces/stateWarnList" = {
REPLACE = "<<optional - This variable contains a list of the tablespace states values in hexadecimal separated by comma, so the TblspCustomHealth parameter of any tablespace which is associated to a specific instance will be in warn state if its value exists in the list defined by users for this pconfig variable. The hex values are integer values you can add the prefix '0x' for any value. For example for the stateWarnList, you can use '2,0x8,0xc'.>>"
},
"/PSO/DB2/<<DB type>>/<<environment name>>/BMC_FORCE/<<DB2 instance name>>/tableSpaces/stateAlertList" = {
REPLACE = "<<optional - This variable contains a list of the tablespace states values in hexadecimal separated by comma, so the TblspCustomHealth parameter of any tablespace which is associated to a specific instance will be in alarm state if its value exists in the list defined by users for this pconfig variable. The hex values are integer values you can add the prefix '0x' for any value. For example for the stateAlertList, you can use '2,0x8,0xc'.>>"
},
"/PSO/DB2/<<DB type>>/<<environment name>>/BMC_FORCE/<<DB2 instance name>>/<<DB2 database name>>/tableSpaces/stateWarnList" = {
REPLACE = "<<optional - This variable contains a list of the tablespace states values in hexadecimal separated by comma, so the TblspCustomHealth parameter of any tablespace which is associated to a specific instance and the specific database will be in warn state if its value exists in the list defined by users for this pconfig variable, the hex values are integer values you can add the prefix '0x' for any value. For example for the stateWarnList, you can use '2,0x8,0xc'.>>"
},
"/PSO/DB2/<<DB type>>/<<environment name>>/BMC_FORCE/<<DB2 instance name>>/<<DB2 database name>>/tableSpaces/stateAlertList" = {
REPLACE = "<<optional - This variable contains a list of the tablespace states values in hexadecimal separated by comma, so the TblspCustomHealth parameter of any tablespace which is associated to a specific instance and the specific database will be in alarm state if its value exists in the list defined by users for this pconfig variable, the hex values are integer values you can add the prefix '0x' for any value. For example for the stateAlertList, you can use '2,0x8,0xc'.>>"
}

Depending on the hexadecimal value set by the user in these rulesets, the KM will set the value of the paraameter TblspCustomHealth.

This parameter used to help user set threshold for parameter TblspState.

Default parameter attributes