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 CICS attribute tables.

  • CICSplex_Service_Class_Analysis wss table will only have data if OMEGAMON is installed and running in the CICS region. It classifies by WLM service class which customers should set up themselves. This allows them to group together transactions and report on them as a group.

  • CICSplex_Plex_Service_Class_Analysis kcpwss is a copy of wss but gives CICSplex wide summaries.

  • For CICS Transaction Gateway there is considerable set up for OMEGAMON CTG to monitor a region and have transaction data. Some covered in config manager, but there needs to be a transaction exit installed. The setup for monitoring CICS TG can be found in IBM Z OMEGAMON for CICS Planning and Configuration Guide especially the first topic listed.

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