Collecting RMF3 Performance Data - ironstream_for_micro_focus_omi - 7.2

Ironstream for Micro Focus® OMi for IBM Z® Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Micro Focus® OMi
Version
7.2
Language
English
Product name
Ironstream for Micro Focus OMi for IBM Z
Title
Ironstream for Micro Focus® OMi for IBM Z® Administration
Copyright
2021
First publish date
2007
ft:lastEdition
2023-08-23
ft:lastPublication
2023-08-23T16:21:59.136387

The standard RMF data collection performed by the agent is a fixed set of RMF performance metrics that are collected and forwarded to the OM server. Tools are provided for configuring and collecting RMF3 performance data and storing that data in a unique data class using the Operations Agent performance sub-agent.

To collect this data, RMF3 monitoring must be enabled on the managed mainframe nodes along with the RMF gatherer (RMFGAT). The RMF distributed data server (GPMSERVE) must also be configured and active on one mainframe node within the Sysplex to be monitored. See Appendix D for information on setting up RMF3 data gathering and the Distributed Data Server.

The steps to configure RMF3 performance data collection are:

  • Determine the RMF3 metric ID and RMF3 resource for each performance metric to be collected. Note that the configuration and collection tools support only RMF3 metrics that return a single value.

  • The configuration file, that defines the performance metrics to be collected, must contain 1 line for each metric to be configured and collected and one or more space or tab characters must separate each item on the line. The configuration file can be found as follows:

    • On Linux in the /etc/opt/OV/share/conf/vp390 directory

    • On Windows in the \conf subdirectory of the Ironstream installation path

Comment lines are permitted and must start with a hash (#) character in column 1. The format for each entry is:

<ID> <MetricName> <RMF3metricID> <RMF3resource> <description>

where:

Format

Description

<ID>

Numeric identification for the metric in OVPA or CODA. The first entry must start with ID 102 and subsequent entries should be incremented by 1. (ID 101 is reserved for the host name.)

<MetricName>

Name that will be used to identify the metric in the OVPA or coda configuration. The name must be no more than 20 characters and must not contain spaces.

<RMF3metricID>

The RMF3 metric ID of the metric to be collected. Use the RMF3 Explorer in the RMF3 web interface to find the RMF3 metric ID. (See "Using the RMF Web Browser Interface" on page 97.)

<RMF3resource>

The RMF3 resource of the metric to be collected. Use the RMF3 Explorer in the RMF3 web interface to find the RMF3 resource.

<description>

Description of the RMF3 metric. The description must not be more than 20 characters.

Example entries:

  1. CSA_UTILIZATION 8D0530 SYS1,*,CSA CSA Utilization

  2. SQA_UTILIZATION 8D0530 SYS1,*,SQA SQA Utilization

  3. SERVICE_UNIT_RATE 8D1FB0 ,BLUE1,SYSPLEX SU Rate for BLUE1

  4. IO_ACTIVITY_RATE 8D0E90 SYS1,*,I/O_SUBSYSTEM IO Rate for BLUE2

  • Run the configuration program ev390addrmf3.pl to configure either the CODA sub-agent or OVPA (if installed) for the RMF3 metrics to be collected:

Linux:

/opt/OV/vp390/bin/ev390addrmf3.pl -domain <mainframe>
-config <configFile> -classname <dataSourceName>
-classnumber <dataSourceNumber>

where:

Windows:

perl \%EV390BIN%\ev390addrmf3.pl -domain <mainframe>
-config <configFile> -classname <dataSourceName>
-classnumber <dataSourceNumber>

Format

Description

<mainframe>

The hostname of the mainframe node where the distributed data server resides

<configFile>

The name of the configuration file created in step 2. Do not use the full path name; the file is assumed to reside in the Ironstream configuration directory.

<dataSourceName>

A unique name for the data source class that will be used in the CODA or OVPA configuration. This will also be the name used to access the data.

<dataSourceNumber>

A unique class number not used by any other data source classes

  • Copy the RMF3_COLLECTION_SAMPLE scheduled action policy in the VP390 Samples policy group to a user defined policy group. Modify the schedule for the desired collection interval and modify the command line parameters of the ev390rmf3_collect.pl command:

Linux:

/opt/OV/vp390/bin/ev390rmf3_collect.pl -ddsserver <mainframe>
-config <configFile> -classname <dataSourceName> [-port <portnum>]

Windows:

perl \%EV390BIN%\ev390rmf3_collect.pl -ddsserver <mainframe>
-config <configFile> -classname <dataSourceName> [-port <portnum>]

where:

Format

Description

<mainframe>

The hostname of the mainframe node where the distributed data server resides

<configFile>

The configuration file name created in step 2. Do not use the full path name; the file is assumed to reside in the Ironstream configuration directory.

<dataSourceName>

The data source class name created in step 3

<portnum>

(Optional) the port number to be used to connect to the distributed data server. This port number must match the HTTP_PORT startup parameter for GPMSERVE on the mainframe. If not specified, the default port is 8803.

  • Assign this policy to the Ironstream Proxy Server node (not the mainframe agent node) and distribute the policy to the OMi management server agent.