RMF is a performance management and reporting tool. The data gathering component of RMF runs as a started task, and its parameters are defined in SYS1.PARMLIB(ERBRMF0n). Member 01 is for Monitor I, 03 is for Monitor II and 04 is for Monitor III. The three monitors are discussed below. If you check out these parmlib members, you can see which RMF records you trap at your site. RMF cuts SMF type 70-79 SMF records for all monitors, and the Monitor III also records information in VSAM records.

RMF runs several data collectors. You can see how many RMF collectors are active with the command


which you can shorten to



Accelerate DB2 Write with zHyperWrite and "EADM™ by Improving DB2 Logs Volumes Response Time:

RMF Monitors

The RMF task gathers performance data, but it is not held in a useful format. You use the RMF monitors to interpret the data, to allow you to check out your system performance

RMF Monitor II

This is a real time monitor that is useful for investigating problems that are happening now. It is mainly used to investigate problems with a single job, task or address space. You invoke it by either using the TSO command


    GFS Advert

or by taking the Monitor II option from the RMF ISPF panel. Once you are in the Monitor II, you see a command list, with a set of PF key shortcuts as shown below.

You can either use the PFkeys, or the command (as shown in the 'name' column) to see each report. Some of the reports are multi-page, and you press enter to page down them. Other reports are single line, and you press enter to get a new line of data. You use the 'quit' command to exit the monitor.

RMF Monitors I and III

These monitors collect data over a longer timeframe, the default is 30 minutes, so you see a consolidated view of events.
You access the monitors from the main RMF ISPF panel. There a lots of different reports, the best way thing to do, is to go in and try some of them. You can use PF7/8 to go up and down each reports. Some of the report field are cursor sensitive. For example if you place your cursor over a specific jobname on the job delay report and press enter, you will get an in-depth analysis for that job.

Some example ISPF reports are

RMF includes a 'Sysplex Data Server', which runs as an identical copy on every system in the sysplex. As each data server communicates with all the other servers, the RMF data can be accessed from any point in the sysplex. As well as the monitors I II and III, including monitor III VSAM data, the RMF reporter can also report on any other SMF data.

Some RMF enhancements in z/OS Version 2.1

RMF has several new reports for the coupling facility. For example, it will report on coupling facilitiy structures that are implemented using SCM or 'Storage Class Memory'. The data is recorded using SMF record type 74-4. The 'Page Data Set Activity' reports provide information about SCM blocks used by the Auxiliary Storage Manager (ASM). The 'Postprocessor Paging Activity' report provides information about shared and high virtual shared and common frames backed on SCM and also provides information about SCM blocks used by ASM.

Channel path detail information is available Coupling over InfiniBand and Coupling Facility Peer channel paths. RMF provides this information in the Postprocessor Coupling Facility Activity report, check out he Subchannel Activity and the CF to CF Activity sections. You can also use the Monitor III Coupling Facility Systems report which has a Channel Path Details section in the Subchannels and Paths pop-up. RMF also stores the newly gathered channel path detail information for coupling facilities into SMF record 74-4.

RMF enhances the Postprocessor Crypto Hardware Activity report to provide activity measurements from the Crypto Express4S (CEX4) card configured in one of the three ways: Cryptographic CCA coprocessor , Cryptographic PKCS11 coprocessor, Cryptographic accelerator.

RMF can report on SMF record 70-1, which describes WorkLoad Manager information about capacity groups. RMF can report on the absolute LPAR capacity limit that can be defined via the logical partition controls of HMC. The Postprocessor Partition Data report and the Monitor III CPC Capacity report display whether either Initial Capping or an absolute LPAR capacity limit was active during a reporting interval.

RMF will also provide a Postprocessor PCIE Activity Report that is available in XML output format. To be able to run this report, you must have at least one of the following; RDMA (Remote Direct Memory Access) over Converged Enhanced Ethernet or zEnterprise Data Compression (zEDC) capability using zEDC Express.

By specifying appropriate ddnames in the job for the Postprocessor output, users can request the following reports about PCI activity in XML output format:

  • Cache Subsystem Activity
  • Channel Path Activity
  • Coupling Facility Activity
  • Enqueue Activity
  • Hierarchical File System Statistics
  • I/O Queuing Activity
  • Page Data Set Activity
  • PCIE Activity Report
  • Shared Device Activity
  • Virtual Storage Activity
  • XCF Activity

Non-Mainframe reporting

RMF XM can use a CIM server to get performance data from a mixture of AIX, Linux and Windows servers. It needs SMF type 104 and within this record, various subtypes exist for different open operating systems

  • 1-12   AIX
  • 20-31  Linux on System X
  • 40-53  Linux on System Z
  • 60-64  Windows

back to top