Introduction

This facility enables you to compare the contents of any number of file ‘pairs’, grouped together into a Comparison Case. You can therefore organise, schedule and execute all file comparisons through a single request whenever it is relevant. File compare is also a good way of comparing report output or message files, once the spooled data has been converted to a physical file using the command Spool_IT or CPYMSGFTF respectively.

Each pair consists of two physical or single format logical files which may have similar file formats. Any field can be compared to any other field in the second file, but the function is designed to identify data differences in different generations of the same file. The comparison and reporting occurs at the field level. As of version 8.0.0, comparison of DDM files is supported.

Comparison may be made between fields which have different names and lengths.
Comparison may be made between field of different types as of version 8.0.0.
Null fields are now supported.

If you wish to verify data in one file against a number of records in another file, for example in a header to lines type relationship, consider using the Data Rules function.

Physical The records in each file will be processed according to the ascending sequence of the RRNs. However no account will be taken of differing RRNs. It is therefore suitable where an identical number of records exist in each file, but they do not have the same RRN. Such a situation may occur after one file has been reorganised (RGZPFM ).

Relative Record Number (RRN) The records in each file will be processed according to the ascending sequence of the RRNs. Any RRNs which exist on one file and not the other will be reported as unmatched records.

Physical Key The records in each file will be processed according to the key specified on the physical file. Any key values which exist on one file and not the other will be reported as unmatched records. This comparison type supports file pairs with all ascending or descending keys and is ideal where the physical file key values are unique. The keys on File A must match in number, Length, Type and Decimal Places.

Logical Key The records in each file will be processed according to the key specified on the logical file. Any key values which exist on one file and not the other will be reported as unmatched records. The keys on File A must match in number, Length, Type, Decimal Places and sequence (all ascending or all descending).