Optional RMF3 Monitoring - ironstream_for_micro_focus_omi - 7.2

Ironstream for Micro Focus® OMi for IBM Z® Administration

Product type
Product family
Ironstream > Ironstream for Micro Focus® OMi
Product name
Ironstream for Micro Focus OMi for IBM Z
Ironstream for Micro Focus® OMi for IBM Z® Administration
First publish date

A set of sample RMF3 monitor policies is included in the Mainframe Samples policy group. These samples are provided as a guide to use OMi monitor policies for monitoring RMF3 metrics. RMF3 metrics return either a single value or multiple values (for example multiple jobs or DASD volumes) depending on the type of metric. The sample monitor policies illustrate the monitoring of both types of metrics.

The RMF3 sample monitor policies execute the ev390rmf3mon.pl script. The monitor name and script parameters must be modified before distributing the monitor policy to customize the specific metrics and server names for your environment.

Before using an RMF3 monitor policy, 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 following parameters in the monitor must be modified:

  1. Monitor Name – The default monitor name used by the monitor script is OS390_RMF3_<metricID>. The same metric ID can exist for multiple RMF3 resources, and in these cases the monitor name should be modified. For example, the percent storage utilization metric ID 8D0530 exists for both CSA and SQA utilization. If monitoring both CSA and SQA storage utilization, then the monitor name must be changed to be unique, for example OS390_RMF3_SQA_8D0530 or OS390_RMF3_CSA_8D0530.

  2. Monitor Program – The RMF3 monitor script uses parameters to determine where to access the distributed data server and what RMF3 resource and metric to retrieve from the distributed data server. The monitor script command format is:


/opt/OV/vp390/bin/ev390rmf3mon.pl -ddsserver <server>
-resource <RMF3resource> -metric <metricID> [-port <portnum>] [-monname <MonName>]


perl \%EV390BIN%\ev390rmf3mon.pl -ddsserver <server>
-resource <RMF3resource> -metric <metricID> [-port <portnum>] [-monname <MonName>]


Format Type



The hostname or IP address where the distributed data server (GPMSERVE) is running


The resource class for the metric. This will vary depending on the metric. The RMF3 web interface explorer can be used to determine the resource class to be used. (See "Using the RMF Web Browser Interface" on page 97.)


The RMF3 metric ID


(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.


(Optional) the monitor name to be used by the monitor script and must match the Monitor Name field in the monitor policy. The default is OS390_RMF3MON_<metricID>, however, if the monitor name does not follow this pattern, then it must be specified in this parameter.

The monitor conditions must be modified for pattern matching of the object field and setting of the correct mainframe hostname. Many of the metrics returned are related to a single system (LPAR) in the sysplex. For this reason, it will be necessary to use pattern matching in the object field to match on the LPAR system ID if it is part of the metric resource in the object field and set the actual mainframe hostname in the node field. The hostname that is set in the node field must match the hostname as defined in OMi.

Metrics related to the sysplex will be reported against the mainframe system where the distributed data server is running unless the condition is modified.

It is recommended that the sample monitor policies be copied to a user defined policy group and modified. After creating the desired RMF3 monitor policies, the policies must be assigned to the OMi management server (not the mainframe agent) before performing the distribution function.