Closed as program error.
Problem Description Error in ibmdi.log Assembly line config name could not be unbinded from MetamergeConfig. In TDI 7.0/7.1 the bug discovered in TDI ibmdi.log indicates the unbind error due to related bug introduced when the MetamergeConfigxml was accessed by multiple threads. The thread will not find since one of previous thread was not removed properly, the error out as the unbind error, and leave garbage in heap memory, might end up "out of memory" as a OOM error. The internal fix was addressed before, fixed the unbind error and never opened the apar # before against previous issue. FYI:The MetamergeConfigXML was never intended to be accessed by multiple Threads, as the methods were not threadsafe. The fix will manage better the mutilple threads at the MetamergeConfigXML level.
The jar file can be provided by the support per a customer's request.
The fix better manages multiple threds.
This is a bug in the TDI code and has been fixed. The official Fix would be made available in 7.0.0-TIV-TDI-FP0009.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels