Considerations on using the Integrity Checker utility

Some considerations apply when using the Integrity Checker utility of IMS Library Integrity Utilities.

When you change a DBD and reorganize DEDB areas by using FPA, Integrity Checker creates new RDEs for the reorganized areas. If reorganization completes successfully, but Integrity Checker fails to create new RDEs, you must take one of the following actions:
- Rerun the reorganization job to create new RDEs for the reorganized areas.
- If you decide not to rerun the reorganization job and to use the original areas, you must delete the RDEs that were created during the reorganization by using the DELETE.DB command of the LICON utility before using the areas.
- If you decide not to rerun the reorganization job and to use the reorganized areas, you must create the RDEs whose creation failed during the reorganization by using the INIT.DB command of the LICON utility before using the areas.
When any of the following error conditions were detected in FPA or Integrity Checker processing, the RDEs are not created:
- Either the return code is equal to or greater than 8 or the processing ends abnormally for one or more areas in the Reload, Change, or Reorg processing.
- The return code is equal to or greater than 8 for the Analyze function even when Reload, Change, or Reorg function completes successfully.
- Integrity Checker fails to create an RDE.
When the randomizer routine, segment edit/compression routine, or both are defined in the DBD library, checksum values of the routines are stored in the RDE. You must make sure that the libraries that contain the correct routines are specified in one of the following DD statements:
- Reload and Change functions
  - IMSRESLB
    When IMSRESLB is not specified, JOBLIB/STEPLIB
- Reorg function
  - JOBLIB/STEPLIB
    If the library that contains the segment edit/compression routine is not concatenated to JOBLIB/STEPLIB, FABL0212W message is issued by Integrity Checker.