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
Description: The SSM can sometime mistakenly report the "Failed to bind to port <port>. Unable to run multiple agents bound to the same port" error message if a old lockfile is present and another process has reuses the PID the previous instance of the SSM had when the lockfile was created. Old lockfiles can appear when the SSM is terminated abruptly.
Local fix
NA
Problem summary
**************************************************************** USERS AFFECTED: All users of the SSM on UNIX platforms. **************************************************************** PROBLEM DESCRIPTION: The SSM main binary checks for a lock file which contained a process id. On UNIX systems if there was an old lock file that contained a process id that was in use then the agent would refuse to start until the lock file was removed, or the process using that ID had completed. **************************************************************** RECOMMENDATION: Upgrade to Fix Pack 8 for SSM 4.0 ****************************************************************
Problem conclusion
This check was completely redundant as the bind command prevents multiple instances of the SSM running on the same port. As a result the lock file is now overwritten with the new process ID. This will stop old lock files from preventing the agent starting. 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
IZ49773
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-04-24
Closed date
2009-05-25
Last modified date
2009-05-25
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:
25 May 2009