X-Verify-Verifies and reports on referential integrity of data

Using X-Verify it is possible to test the referential integrity of the production data based upon the data model. X-Verify takes individual records of the detailed/lowest level files in the production system and verifies the existence of the relevant parent records based upon the data model relationships.

Any missing parent record is reported accordingly in an exception report. This process is carried for each detail entity in the production system and through all levels of the data model for each entity or physical file. In addition to reporting these referential integrity exceptions, X-Verify has the capability of automatically fine-tuning the data model based upon the results of the validation process. In this way it is possible to produce a highly accurate data model based upon the actual implementation of the production data.

Key Features

• Select & Edit the X-Rev derived Data Model to your precise requirements
• Totally integrated with X-Analysis Tool Suite
• Automated and repeatable
• RPG based I/O for efficiency on large databases.
• Orphaned records reports
• Auto adjust data model from results

Instant Test Data Subsets From Live Data...

An entire 'blank' test library is built by X-Subset based upon the data model produced in the first phase. The second phase has two possible methods of selecting the records to use for subsetting. This is either a specified number of records of a file that has no dependent data, or all of a predefined selection of these detailed records, which have been identified by specifying an owning or parent file with pre-seeded master records. In this way it is possible to create test data subsets from the bottom up, or from the top down. A number of records is then extracted from the lowest level detail file of the production system and written to the test library. Each data modeling relationship in turn is then examined and the required data from the production system is written into the relevant place in the test library. The data model is then referenced to check that all referenced records have been included. It completes this process across the entire database - enabling the construction of test data libraries with no 'broken inks' between all related records.