IZ52864: SSM logging logic uses too much CPU

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

• This has been found indirectly by customer observation but the
  root cause has now also been identified. The TrunkWritez
  function calls the FormatPrefix function for every target
  regardless of whether the log line is going to be actually
  written. FormatPrefix is quite an CPU expensive function and
  should only be called if we are going to write to the log file.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of the SSM.
  ****************************************************************
  PROBLEM DESCRIPTION:
  The SSM logging code did not check if the log line was to be
  logged to any target before doing some formatting. That
  formatting used quite CPU intensive functions. This meant that
  when the SSM was running in normal mode debug level log messages
  were causing more CPU consumption than necessary.
  ****************************************************************
  RECOMMENDATION:
  Upgrade to Fix Pack 8 for SSM 4.0
  
  ****************************************************************
  

Problem conclusion

• Introduced a check that makes sure a line is going to be sent to
  a log target before executing the CPU intensive system calls.
  
  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 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 PSY

     UP