List of examples of changing the metric collection environment and the required operations

Mainframe Analytics Recorder User Guide

Version

10.1.x

Audience

anonymous

Part Number

MK-92HC226-08

ft:lastEdition

2026-01-30

The following table lists examples of changing the metric collection environment and the required operations.

Table. List of examples of changing the metric collection environment and the required operations
Examples of changes	Whether operation is required
Examples of changes	Scan	Change of metric collection parameters	Execution of `REFRESH`
Adding a storage system to the collection targets	Required (Scan the storage systems to be added.)	Required	Required
Adding volumes not in the disk configuration definition file to the collection targets	Required (Scan the volumes to be added.)	Required if the `LDEVFILT` parameter is specified.
Changing the collection scope within volumes in the disk configuration definition file	Not required	Required
Adding a volume added to an SMS storage group to the collection targets	Required (Scan the SMS storage group again.)	Not required
Excluding from the collection target volumes that were deleted from an SMS storage group	Required (Delete the disk configuration definition file, and then scan the storage system again.)	Not required
Excluding volumes that were deleted from the system from the collection targets	Required (Delete the disk configuration definition file, and then change the range of scanning, and scan the storage system again.)	Not required
Adding I/O destination devices	Required (Scan the volumes to be added.)	Required
Changing the interval and metrics	Not required	Required

Tip: When you change metric collection parameters, execute the DISPLAY command to check the parameter file name (member name) of the running metric collection program.

F RS1,D,PARM

Tip: When you want to change the member names of metric collection parameters, specify member names by using the MEMBER parameter of the REFRESH command.

F RS1,RE,M=P150325