DevOps Lifecycle – Tune

Use Strobe to identify program statements that consume excessive CPU

  • Identify SQL statements and Db2 system services that cause excessive CPU or wait time
  • View resources and percentage of CPU time used within modules and control sections, display procedure names and statement numbers, and provide complete line of source code
  • Leverage a treemap to easily understand how applications use CPU data without having to parse through excessive data clutter
  • Use Strobe Profile Summary Compare:
    • to create an artifact for reporting
    • for compiler, Db2, CICS, and IMS upgrades to confirm performance is within expectations when analyzing different program coding alternatives
    • to quantify performance improvements realized when converting VSAM datasets to IAM datasets