Fixes are available
Closed as program error.
PMI settings do not work in datacollector_global_custom.properties When PMI settings (am.was6custompmi.settings.1=..., etc) are specified in datacollector_global_custom.properties, they do not take effect.When exactly the same datacollector_global_custom.properties file is copied to datacollector_custom.properties in the app server "custom" directory, the PMI settings requested work as expected. BTW, the same problem exists for distributed datacollectors! I ran through all the unit tests for this feature on the toolkit and everything worked just fine. However, when it is run with the shared data collector, there is one situation that fails. Any property in datacollector_global_custom.properties will be applied to all DCs except if a property of the same name already exists in the server datacollector.properties. The datacollector.properties file that is distributed with the product contains two PMI properties am.was6custompmi.settings.1=threadPoolModule=3,4 am.was6custompmi.settings.3=servletSessionsModule=7,17,6,14,9,1, 11,10,13,12,2,4,8,15,16 Any other PMI modules can be overridden in global except these two. The native toolkit loads all properties files in a predefined order (global, base, local) and does not overwrite a property that already exists. The DC reads the properties files but does not honor that order properly.
The only workaround is to supply these two properties in the local rather than the global template.
Global datacollector properties do not override datacollector,properties if property already exsists.
Order of property files merge is corrected.
Reported component name
ITCAM WAS ZOS D
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
ITCAM WAS ZOS D
Fixed component ID
Applicable component levels