Skip to Content

Missing, incomplete, or duplicate records

The only record type that UIE requires is RMF type 70. The output that UIE creates contains intervals only for those systems that have type 70 records.

However, if any other record types are missing or incomplete, some parameters in the UIE output can be less accurate or missing altogether. For example, if type 42, subtype 6 records are missing, distribution of some DASD activity by workloads can be less accurate, and unaccounted activity on some devices might be higher.

Related topics

RMF-and-SMF-data-collection

Processing performance data.

To generate useful models, some minimum sets of records must be present. The most typical cases are as follows:

  • Only type 70 records are present—only system-wide CPU related information will be in the generated XML model and the Visualizer file.
  • Only RMF type 70, 71, 72, 73, 74, and 75 records are present—only XML model TYPE=PGSCL or REPORT can be used. The workloads that are created do not have any I/O activity.
  • Only RMF type 70:75 and SMF type 30 records are present—batch applications can be created.

Duplicate RMF records for types 70, 71, 72, 74, and 75 are automatically detected and discarded. However, automatic detection is not enabled for other record types. To detect and eliminate type 30 duplicate records, you need to use the DELETEDUPREC command (described in Using-Command-filters).

Warning

Important

The DELETEDUPREC command is resource intensive. We recommend that you use DELETEDUPREC only if you suspect that the duplicate records exist. UIE does not detect duplicate records (for example, 42, 99, 101, 110, and so on) because that requires unreasonable additional resources.

Automatic detection is enabled only for the key RMF records because eliminating duplicate records can consume a lot of system resources, which can significantly increase processing time. You should request automatic detection only it if you suspect record duplication has caused erroneous results.

Warning

Important

BMC AMI Ops Monitor for CMF and RMF both generate type 70 to 78 records. However, due to time stamp synchronization differences, these records are not exact duplicates and are not automatically filtered by UIE. This situation causes the double counting of some metrics, including CPU utilization and LPAR dispatch. UIE detects the simultaneous presence of BMC AMI Ops Monitor for CMF and RMF records and issues an error message, but UIE cannot automatically determine which records should be ignored.

If you are collecting both BMC AMI Ops Monitor for CMF and RMF data, specify the BYPASSREC command to indicate to UIE which data source should be bypassed. For more information, see BYPASSREC for further information.

 

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

Universal Information Exchange 2.1