Whenever S6BSMESD finds that two or more concurrent sorted internal records exactly match, there is a strong possibility that these represent duplicate SMF records. These get counted as part of the current system ID, date, and time range, and also as duplicates by record type.
The S6BSMESD member of the JCL data set distributed with TIBCO Object Service Broker contains sample JCL required to run this utility. This sample is provided as a reference only; modify the JCL for your needs.
This input file contains data from a 24 hour period split over two days. Neither SMF type 2 nor type 3 records are included in REC.COUNT; their counts are provided separately on the totals line.
This input file contains a number of records that are similar or duplicate. Their total count appears below the overall totals and forms a subset of the overall totals. A breakdown is provided in the form of record_type followed by record_count. In this example, there are only a few different record types, which indicates that these types are being produced in pairs or multiples with similar contents.
If there were a much larger number of different record types, it would indicate that certain time ranges are included twice or more within the file, making it unsuitable for accounting.
In cases where duplicated ranges are suspected and the input file is not re-sorted, S6BSMFCH helps determine the starting record number and counts of duplicated date-time ranges. S6BSMFCH produces a similar report, except that the data is reported in the sequence found in the file (no sort).
TIBCO Object Service Broker for z/OS Monitoring Performance for complete information about collecting and reporting on SMF records.