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

Update the ODP collection configuration

  1. On z/OS, edit the ODP collection configuration member RKANPARU(KAYOPEN) to specify the attribute groups required by the Instana support for Db2.
collections:
  - product: kd5
    table: db2lkconf
    interval: 0
    destination:
      - pds
      - open
  - product: kd5
    table: dp_ci_excs
    interval: 0
    destination:
      - pds
      - open
  - product: kd5
    table: dp_im_conn
    interval: 0
    destination:
      - pds
      - open
  - product: kd5
    table: dp_sy_exc
    interval: 0
    destination:
      - pds
      - open
  - product: kd5
    table: opersys
    interval: 0
    destination:
      - pds
      - open

  1. Reload the configuration of collection tasks to reflect the updated KAYOPEN member.

    For each job that runs an OMEGAMON monitoring agent (including the monitoring server job), enter the following MVS MODIFY system command:

    F <job_name>,KPQ RELOAD_CONFIG,KAY
    

    Replace <job_name> with the corresponding job name for each agent: for example, OMEGDS.

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