Skip to Content

Default language.

Running CMF and RMF on the same system

You can run BMC AMI Ops Monitor for CMF on a system where you are also running RMF, but you should be aware of the following considerations:

  • Both CMF and RMF Extractors produce identical type 70 through type 79 records, but CMF should not write records to an SMF data set or SMF logstream if BMC AMI Ops Monitor for CMF and RMF are to be active at the same time.

    RMF cannot distinguish between CMF-generated SMF records and RMF-generated records. When RMF reads SMF data that contains both CMF- and RMF-generated records, the data will be duplicated and the RMF postprocessor will produce erroneous and misleading reports.

In contrast, CMF Analyzer can distinguish between the two, and thus this problem can not occur.

Related topics

Preprocessing of Extractor data setsDEVICE-Extractor-control-statements

Collecting-data-using-the-BMC-AMI-Ops-Monitor-for-CMF-Extractor

BMC-AMI-Ops-Monitor-for-CMF-similarities-with-IBM-RMF

If you have inadvertently written CMF and RMF data together, you can use the CX10CVBS copy utility to separate the records.

  • CMF can start and stop I/O monitoring of devices other than tape and DASD. When this feature is activated, CMF makes sure that RMF’s control of the channel measurement blocks for nontape and non-DASD devices is maintained. RMF assumes that it has exclusive use of all nontape and non-DASD CMBs. If RMF is active and sampling nontape and non-DASD device classes, CMF does not perform start or stop I/O monitoring of this kind.
Warning

Important

CMF

 device monitoring is controlled by the CLASS parameter of the Extractor DEVICE control statement. If SMF type 74 records that are compatible with those produced by RMF are desired, CLASS should be the only parameter used.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Monitor for CMF 6.5