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 z/OS attribute tables.

  • The tables Common Storage Utilization History m5stgcdth and Real Storage Utilization History m5stgfdth require GPMSERVE configuration. The IBM Z OMEGAMON Monitor for z/OS 5.6: Planning and Configuration Guide has the documentation. See the section "Enabling RMF Data Collection".

  • Table System_CPU_Utilization syscpuutil requires RMF to be configured on the LPAR to acquire some of the data reported which should be standard for any LPAR.

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