≡ Menu

Tivoli Business Service Manger 4.1 Interim Fix 007 Available

in IBM, Implementation, TADDM, TBSM, Tivoli, Usability

A new TBSM 4.1 Interim Fix (007) is available on the support download site here. Ensure your TADDM installation is patched to the correct FP or IF level as well.

This version provides fixes to IBM Tivoli Business Service Manager 4.1 Discovery Library toolkit.

* Fixes that are included in this Interim Fix:

164321 – TBSM does not reflect deleted resources in TADDM business applications
IY98472- Problems handling deleted base classes in TADDM metadata.
IY99645- Performance improvements for TADDM imports
163212 – Namespace missing from WSPort
164995 – DL_TmpFile_CleanupInterval min value set to 4320
165159 – DB2 resources from latest zOS DLA are not displayed

TBSM DOES NOT REFLECT DELETED RESOURCES IN TADDM BUSINESS APPS (164321)

Resources that are removed from business applications in TADDM are not removed from the service views in TBSM following a bulk import.

PROBLEMS HANDLING DELETED CLASSES IN TADDM METADATA (IY98472)

TBSM maintains a list of classes that it collects from TADDM. Recent fixpacks to TADDM have implemented changes in the common data model, these changes included the deletion of classes that previously existed. TBSM continued to query for information on the deleted classes, resulting in exceptions that stopped processing.

PERFORMANCE IMPROVEMENTS FOR TADDM IMPORTS (IY99645)

This fix implements a number of changes to the methods used to import data from TADDM. These changes require that TADDM be at FP3 or higher.

NAMESPACE MISSING FROM WSPort (163212)

WSPort objects missing namespace attribute because of method of checking object types using base class attribute list.

DL_TmpFile_ClenaupInterval MIN VALUE SET TO 4320 (164995)

The minimum allowed value for DL_TmpFile_ClenaupInterval has been changed to 4320 seconds (3 days). This was changed to ensure that data would be maintained for problem determination.

DB2 RESOURCES FROM LATEST ZOS DLA ARE NOT DISPLAYED (165159)

Changes in the latest zOS DLA resulted in DB2 resources not being processed correctly.

Next post:

Previous post: