Readmes are available
IBM Tivoli 4.0.0-TIV-SSM-FP0010
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 program error.
Error description
It seems that some ASM(s) or other "unknown" thirdparty code may change the current working directory of the SSM. This means that after a cold or warm boot, the SSM can't find it's subagents. To reproduce this bug you must 1. Start the agent without using the init.ssmagent script (usually AIX). Because the init script implements a workaround for this issue. 2. Trigger the unknown code which changes the working directory of ssmagent.bin (steps unknown).
Local fix
Start the agent using init.ssmagent; OR env LD_LIBRARY_PATH=/full/path/to/ssm/bin ssmagent (Unix/Linux); OR env LIBPATH=/full/path/to/ssm/bin ssmagent (AIX)
Problem summary
**************************************************************** USERS AFFECTED: AIX uses of SSM 4.0 **************************************************************** PROBLEM DESCRIPTION: On AIX, after running for a day or two, and a coldboot, the SSM could no longer load any subagents. Analysing /proc showed that the CWD of ssmagent.bin had changed to something completely unrelated to the SSM, causing all subsequent library (subagent) loads to fail. **************************************************************** RECOMMENDATION: Upgrade to Fix Pack 8 for SSM 4.0. ****************************************************************
Problem conclusion
Installing Fix Pack 8 and later will force the full path of the SSM bin directory to be inserted into LD_LIBRARY_PATH (LIBPATH on AIX). This ensures that the current working directory does not affect the SSM's ability to find subagent binaries. The fix for this APAR is contained in the following maintenance packages: | fix pack | 4.0.0-TIV-SSM-FP0008
Temporary fix
Comments
APAR Information
APAR number
IZ55726
Reported component name
NETCOOL SYS SVC
Reported component ID
5724P4300
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2009-07-22
Closed date
2009-07-27
Last modified date
2009-07-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
NETCOOL SYS SVC
Fixed component ID
5724P4300
Applicable component levels
R400 PSN
UP
Document Information
Modified date:
27 July 2009