Previous Topic: (Optional) Check Space Used by the TSF Database ManuallyNext Topic: Automate the Reclaim Free Space Process

Managing Databases › Time Series Facility Database › How to Customize the Time Series Facility Database › Manage Stored Metric Data

Manage Stored Metric Data

TSFPARMS member parameters in CETJOPTN let you control and reduce the amount of data being stored for all metrics that TSF collects. If you monitor multiple subsystems or you use multiple data feeds, you can alter the metric management parameters to minimize the amount of stored data. Alternatively, use these parameters to increase the TSF data storage capacity by using larger TSF data tables in the CA Chorus database MUF.

CA Chorus ships with default settings. After initial usage, we recommend that you review the defaults and adjust accordingly.

The TSF database is tiered so that data becomes less granular the longer it is stored. Records enter the TSF database at tier one, and roll into tier two and three as they reach their expiration age. If tier three is not specified, the records are deleted from the database. TSFPARMS member parameters in CETJOPTN let you control the expiration age of each tier.

The tier parameters are divided into the following groups so that the metrics can be processed differently:

Note: CA SYSVIEW and NETPERF parameters apply to CA Chorus Infrastructure Management for Networks and Systems.

Global

Applies to all metric sources.

Detector

Identifies a group of CA Chorus for DB2 Database Management-specific values that differ from the global settings. If set, these values override the global tier parameters.

NETPERF

Identifies a group of CA NetMaster NM for TCP/IP-specific values that differ from the global settings. If set, these values override the global tier parameters.

Security

Identifies a group of CA Chorus for Security and Compliance Management-specific values that differ from the global settings. If set, these values override the global tier parameters.

Storage

Identifies a group of CA Chorus for Storage Management-specific values that differ from the global settings. If set, these values override the global tier parameters.

SYSVIEW_CICS

Identifies a group of CA SYSVIEW-specific values for Customer Information Control System (CICS) Transaction Server that differ from the global settings. If set, these values override the global tier parameters.

SYSVIEW_IMS

Identifies a group of CA SYSVIEW-specific IMS values that differ from the global settings. If set, these values override the global tier parameters.

SYSVIEW_MVS

Identifies a group of CA SYSVIEW-specific values (z/OS, JES2, JES3) that differ from the global settings. If set, these values override the global tier parameters.

SYSVIEW_WEBMQ

Identifies a group of CA SYSVIEW-specific values (Websphere MQ) that differ from the global settings. If set, these values override the global tier parameters.

Follow these steps:

  1. Open the TSFPARMS member of CETJOPTN and edit the global group to define the metric management tier parameters:
    1. Review and customize the following global tier parameters:
      MMT1EXPIRY=nn[D|W|M|Y]

      Specifies the expiration age for tier one in number of days, weeks, months, or years. Records that reach their tier one expiration age roll into tier two. No resolution is specified for tier one. Records enter the TSF database at this tier. The agent providing the data sets the resolution.

      Default: 14D (Global, Detector, Storage), 1D (Security) and 7D (NETPERF and all CA SYSVIEW options).

      MMT2RESOLUTION=nn[M|H]

      Specifies the time resolution for tier two samples in hours or minutes. Tier two records contain samples with a resolution equal to this value.

      Values: M (minutes): 1, 5, 15, 30, or 60. H (hours): 1, 2, 4, 12, or 24

      Default: 4H (Global, Detector, Storage), 30M (Security), and 1H (NETPERF and all CA SYSVIEW options).

      Note: Tier resolution times must increase in size from one tier to the next.

      MMT2EXPIRY=nn[D|W|M|Y]

      Specifies the expiration age for tier two in number of days, weeks, months, or years. Records that reach their tier two expiration age roll into tier three. If tier three is not specified, the records are deleted from the TSF database.

      Default: 3M (Global, Detector, Storage), 14D (Security), 8D (NETPERF) and 7D (all CA SYSVIEW options).

      Note: Tier expiration ages must increase in age from one tier to the next. The age of the last tier is used to expire records from the TSF database, regardless of the tier where the records reside.

      The default expiration age and resolution for the metric records are defined. To override these values, specify Detector, Infrastructure Management, Security, or Storage parameters.

    2. (Optional) If you need more than two tiers, duplicate the MMT2EXPIRY and MMT2RESOLUTION parameters and customize them as MMT3EXPIRY and MMT3RESOLUTION. You can define up to five tiers, and they must be contiguous.

      Note: Security includes MMT3 settings by default (MMT3RESOLUTION=4H and MMT3EXPIRY=3M).

  2. Review and customize the discipline-specific tier parameters noted in Step 1a to define the following information:
  3. Identify when metric management starts by editing the following parameter:
    MMSTARTTIME=hhmm

    Specifies the preferred time in hours (hh) and minutes (mm) to start the daily metric management execution.

    Range: 0000 (midnight) to 2359

    Default: 0200

    The metric management start parameter is updated.

    Note: You can also start metric management on demand through the following console command: F CHORTSF,TSFMETMAN

  4. Update the maximum metric management runtime by editing the following parameter:
    MMMAXRUNTIME=hhmm

    Specifies the maximum runtime of one metric management in hours (hh) and minutes (mm). With MMSTARTTIME, this parameter effectively limits the time frame that the metric management runs.

    Range: 0000 to 2400

    Default: 0400

    The metric management runtime is updated.

    TSFPARMS is updated and the metric management parameters are customized to control stored metric data.

Note: After each metric management execution, we recommend that you reclaim free space using the CHTSDBMT member of CETJJCL.

For more information about automating the free space reclaiming, see Automate the Reclaim Free Space Process.

Example 1: Metric Management Sample Tiers Defined

MMSTARTTIME=0200
MMMAXRUNTIME=0400
*
<GLOBAL>
MMT1EXPIRY=14D
MMT2RESOLUTION=4H
MMT2EXPIRY=3M
*
<DETECTOR>
MMT1EXPIRY=14D
MMT2RESOLUTION=4H
MMT2EXPIRY=3M
* Tier 1 contains hourly data for 14 days. Tier 2 contains 4 hours of data and expires after 3 months.
<SECURITY>
MMT1EXPIRY=1D
MMT2RESOLUTION=30M
MMT2EXPIRY=14D
MMT3RESOLUTION=4H
MMT3EXPIRY=3M
* Tier 1 contains hourly data for 1 day. Tier 2 contains 30 minutes of data and expires after 14 days. Tier 3 contains 4 hours of data and expires after 3 months.

Example 2: Metric Management: All Tier Parameters

In this example, the Detector tier parameters are set to a longer time with two tiers. The Security tier parameters are set to a shorter time with four tiers. Global, Storage, SYSVIEW and NETPERF tier parameters are set to default values:

<GLOBAL>
MMT1EXPIRY=14D
MMT2RESOLUTION=4H
MMT2EXPIRY=3M

<DETECTOR>
MMT1EXPIRY=1M
MMT2RESOLUTION=12H
MMT2EXPIRY=4M

<SECURITY>
MMT1EXPIRY=1D
MMT2RESOLUTION=5M
MMT2EXPIRY=7D
MMT3RESOLUTION=30M
MMT3EXPIRY=1M
MMT4RESOLUTION=4H
MMT4EXPIRY=3M

<STORAGE>
MMT1EXPIRY=14D
MMT2RESOLUTION=4H
MMT2EXPIRY=3M

<SYSVIEW_CICS>
MMT1EXPIRY=7D
MMT2RESOLUTION=1H
MMT2EXPIRY=8D

<SYSVIEW_IMS>
MMT1EXPIRY=7D
MMT2RESOLUTION=1H
MMT2EXPIRY=8D

<SYSVIEW_MVS>
MMT1EXPIRY=7D
MMT2RESOLUTION=1H
MMT2EXPIRY=8D

<SYSVIEW_WEBMQ>
MMT1EXPIRY=7D
MMT2RESOLUTION=1H
MMT2EXPIRY=8D 

<NETPERF>
MMT1EXPIRY=7D
MMT2RESOLUTION=1H
MMT2EXPIRY=8D

More information

Increase Data Set Space Allocations

TSF Database Recommendations