IZ43340: programmable causes the SSM to use 100% CPU if execution takes >10 sec

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

• Product: SSM
  Release: 4.0
  Severity: 2
  
  Environment: Unix
  
  Current behaviour/symptoms/Problem description:
  Executing a script which takes longer than 10 seconds to
  complete will cause the Agent to consume 100% CPU
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Netcool/SSM 4.0 on Unix/Linux
  ****************************************************************
  PROBLEM DESCRIPTION:
  If a process spawned from programmable was left to run for more
  than 10 seconds, the SSM would start using 100% of one CPU
  after that 10 seconds and not cease until the process exited.
  The problem only occurred on Unix/Linux.
  ****************************************************************
  RECOMMENDATION:
  Upgrade to Fix Pack 7 for SSM 4.0.
  ****************************************************************
  

Problem conclusion

• The timeout parameter to select() was not being reset to 10
  seconds if and when it timed out every 10 seconds waiting for
  input. So after the first 10 seconds it would use a timeout of 0
  seconds and spin a CPU. The fix was to forcefully reset the
  timeout to 10 seconds on every iteration so as to avoid timing
  out for 0 seconds and hence spinning.
  
  The fix for this APAR is contained in the following maintenance
  packages:
   | fix pack | 4.0.0-TIV-SSM-FP0007
  

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