Readmes are available
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001
APAR status
Closed as change to accomodate OEM Vendor's code.
Error description
We have reason to believe the SSM is suffering from this Windows anomaly: http://support.microsoft.com/kb/173260/ which Microsoft claim will not be fixed. Several times we have seen pthread functions stuck in WaitForSingleObject even after we know for certain that the object being waited for has been signalled. This is probably due to the low-level process probing, and loading of so many libraries (like perfmon provider DLLs) that occasionally use the Windows debugging API even in production.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of SSM 4.0 on Microsoft Windows **************************************************************** PROBLEM DESCRIPTION: We suspect the SSM is suffering from this Windows anomaly: http://support.microsoft.com/kb/173260/ which Microsoft claim will not be fixed. Several times we have seen pthread functions stuck in WaitForSingleObject even after we know for sure that the object being waited for has been signalled. This is probably due to the low-level process probing, and loading of so many libraries (like perfmon provider DLLs) that occasionally use the Windows debugging API even in production. **************************************************************** RECOMMENDATION: Upgrade to Fix Pack 11 for SSM 4.0. ****************************************************************
Problem conclusion
Upgraded the SSM to IBM Win32 Pthreads v4.0.5 which adds a workaround for KB173260. The fix for this APAR is contained in the following maintenance packages: | fix pack | 4.0.0-TIV-SSM-FP0011
Temporary fix
Comments
APAR Information
APAR number
IZ85677
Reported component name
NETCOOL SYS SVC
Reported component ID
5724P4300
Reported release
400
Status
CLOSED OEM
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2010-09-24
Closed date
2010-10-21
Last modified date
2010-10-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R400 PSN
UP
Document Information
Modified date:
21 October 2010