Designing the operation

Mainframe Analytics Recorder User Guide

Version
10.1.x
Audience
anonymous
Part Number
MK-92HC226-08
ft:lastEdition
2026-01-30
Design the operation for collecting metrics.
According to the following table, design the operation for collecting metrics.

Items to be designed

Item to be designed

Description

Metrics to be collected

Of the metrics for LDEVs, MPUs, ports, parity groups, and the top 20 resources with the highest MP usage, determine which metrics are to be collected.

Metric collection scope

Determine the metric collection scope.#1

  • For MPUs, ports, parity groups, and the top 20 resources with the highest MP usage:

    Determine the collection scope for each storage system.

  • For LDEVs:

    Determine the collection scope by specifying device numbers, volume serial numbers, or SMS storage group names.

    When multiple subchannel sets are used, determine the volumes of which subchannel set are the target.

    For Non Gen'ed volumes (volumes that are not included in the I/O configuration definition of the host), determine the collection scope by specifying storage systems or CUs.

Metric collection interval

Determine the metric collection interval from the following viewpoints:

  • Whether to synchronize the interval with the SMF global recording interval
  • Whether to synchronize the interval with the RMF interval
  • Whether to uniquely set the intervals and synchronization time

I/O destination devices

I/O destination devices are required for each storage system for which performance information is to be collected.

Consider the following when determining the I/O destination devices:

  • Prepare a dedicated volume that is not used by other systems.
  • Taking into account availability, specify two or more I/O destination devices for each storage system.
  • If LDEV information is collected from a lot of volumes, you can shorten the time required to collect the information by increasing the number of I/O destination devices. Determine the number of I/O destination devices for each storage system, according to the ratio of the number of the volumes for which LDEV information is to be collected.

Scan scope of the storage system

Scan the collection range of LDEVs (excluding Non Gen'ed volumes) and I/O destination devices.

Prefix of the disk configuration definition file

Determine a prefix for each operation.#2

Prefix: 25 or fewer characters prefix

SMF record type

If you do not use the default value that is set by the system symbol &RSRTYPE, determine the SMF record type.

Required memory size and dataset disk space

Calculate the required memory size and the required disk space for the SMF dataset and for the disk configuration definition file dataset.

#1
For details on how to determine the metric collection scope, see About scope of metric collection.
#2

If you want to install and use MAR in the same system as Business Continuity Manager or Tiered Storage Manager for Mainframe, specify a character string different from the prefix of Business Continuity Manager or Tiered Storage Manager for Mainframe as the prefix of the disk configuration definition file. If the same prefix is used, the product might operate abnormally.

  • Acquiring disk configuration information