z Open Dataz Open Data
Overview
  • odp-elastic-samples
  • odp-prometheus-samples
  • cics-performance-analyzer-elastic
  • ims-performance-analyzer-elastic
  • transaction-analysis-workbench-elastic
  • ims-connect-extensions-analysis-splunk
  • Db2 Query Monitor Starter Dashboards
  • Instana Configuration Topics
GitHub
Overview
  • odp-elastic-samples
  • odp-prometheus-samples
  • cics-performance-analyzer-elastic
  • ims-performance-analyzer-elastic
  • transaction-analysis-workbench-elastic
  • ims-connect-extensions-analysis-splunk
  • Db2 Query Monitor Starter Dashboards
  • Instana Configuration Topics
GitHub
  • Instana Configuration

    • Overview

      • Introduction
      • What's new
      • Configuration Steps
    • Configuring each OMEGAMON Agent

      • Db2 Agent

        • Update the ODP collection configuration
        • Create historical data collections
        • Activate controls to drive NTH collection
      • CICS and CICS Transaction Gateway Agents

        • Update the ODP collection configuration
        • Create historical data collections
        • Activate controls to drive NTH collection
      • z/OS Agent

        • Update the ODP collection configuration
        • Create historical data collections
        • Activate controls to drive NTH collection
      • IMS Agent

        • Update the ODP collection configuration
        • Create historical data collections
        • Activate controls to drive NTH collection
      • JVM Agent

        • Update the ODP collection configuration
        • Create historical data collections
        • Activate controls to drive NTH collection
      • MQ Agent

        • Update the ODP collection configuration
        • Create historical data collections
        • Activate controls to drive NTH collection

Activate controls to drive NTH collection

Tips

To ensure that Near Term History, NTH, is collecting data properly, some specific subsystem and/or agent configuration changes may be necessary. These should be set up via the E3270UI or TEP user interfaces.

The following changes are required for some of the Db2 attribute tables.

For ZOS System Statistics opersys attributes - ZOSMETRICS=YES should be set in DSNZPARM. From the E3270UI as described in OMEGAMON for Db2 Performance Expert on z/OS 5.5, choose Option H for DSNZPARM.

From there, top right of the next panel, choose *-OTHERS where you'll be redirected to this panel OMEGAMON for Db2 Performance Expert on z/OS 5.5 where you can change the ZOSMETRICS parm to YES in the collection under the label From DSN6SPRM.

A similar process can be followed from the Tivoli Enterprise Portal to make this change.

Tips

Parameter ZOSMETRICS must be set to YES for enabling DB2 to retrieve data from the RMF interface. If ZOSMETRICS is not set to YES, you might see negative Operating System CPU data. ZPARM ZOSMETRICS in DSN6SPRM.

Last Updated: 7/20/26, 9:31 AM
Contributors: Jim Porell, David Dai
Prev
Create historical data collections