IZ76098: SSM on Unix/Linux fails to start during system boot after FP8/FP 9 is installed

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

• The Fixpack 8 and 9 are referring to /etc/init.d instead of
  /opt/netcool/ssm/bin for the 'ssmagent' binary.
  

Local fix

• Options :
  
  1) Modify the init script by adding the absolute path to EXEDIR,
  FULLCFGDIR variables as Fixpack 7
  # ls -l /etc/rc3.d/S98ssmagent
  lrwxrwxrwx   1 root     other         25 May 13 03:30
  /etc/rc3.d/S98ssmagent -> /etc/init.d/init.ssmagent
  #
  
  2) Delete the existing /etc/rc3.d/S98ssmagent softlink pointing
  to
  /etc/init.d/init.ssmagent file and create the softlink to point
  to
  /opt/netcool/ssm/bin/init.ssmagent
  # ln -s /opt/netcool/ssm/bin/init.ssmagent
  /etc/rc3.d/S98ssmagent
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of SSM 4.0 FP8/9 on Unix/Linux
  ****************************************************************
  PROBLEM DESCRIPTION:
  SSM fails to start during system boot after FP8/FP9 is
  installed.
  ****************************************************************
  RECOMMENDATION:
  Upgrade to Fix Pack 10 for SSM 4.0.
  ****************************************************************
  

Problem conclusion

• Recent changes to init.ssmagent in FP8/FP9 made it unable to
  find the real SSM bin directory if run as a multiply-indirect
  symlink:
    symlink --> symlink --> ... --> init.ssmagent
  This has been fixed as init.ssmagent can now handle any number
  of symlinks.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 4.0.0-TIV-SSM-FP0010
  

Temporary fix

Comments

APAR Information

• 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