IBM Support

TBSM 6.2 - How to remove service instances with SLA tracking

Question & Answer


Question

If a TBSM 6.2 service instance has accumulated SLA tracking, while trying to remove it, either by command line or through GUI interface, then this does not get deleted and it returns transaction rollback errors messages or, although it disappears from UI, it is still present in the database.

Answer

This is a known issue in TBSM 6.2 for which the following APAR has been opened and it will be fixed in TBSM 6.2 Fix Pack 3.
APAR IJ22338  TBSM 6.2 REMOVAL OF SERVICE INSTANCES WITH SLA TRACKING DOES NOT WORK WITHOUT DISABLING SLA
As a workaround, the following steps can be followed:
  • login to Impact UI -> go to Policies and open ClearTypeCaches policy.
  • within this policy, search for line 21; it should be this one:

 log("<ClearTypeCaches> clearing: "+TypesToClear);

  • after it add the following if statement: 

if(MaxNum == NULL){

    MaxNum =1;

}

 So that section should become:

 [..]

log("<ClearTypeCaches> clearing: "+TypesToClear);

 if(MaxNum == NULL){

    MaxNum =1;

}

i = 0;

  if (TypesToClear[i] <> NULL) {

    runFunction0=true;

  }

[...]

  •  save the policy and try to remove the service with SLA again.

      

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"SSSPFK","label":"Tivoli Business Service Manager"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":""}]

Document Information

Modified date:
30 January 2020

UID

ibm11285108