Examples of IMS Database Repair Facility usage

Scenario 1: Changing a pointer

Your installation experiences a power failure. Afterward, you encounter an abend while you use the IMS database. The Pointer Checker utility shows that one of your pointers is invalid. From the Pointer Checker reports, you determine the correct value of the pointer.

You can fix this problem easily with IMS Database Repair Facility. You no longer need to restore the entire database from a backup that was made before the power failure.

Instead, take the database offline, run IMS Database Repair Facility, and correct the pointer in error.

Scenario 2: Repairing data

You realize that an incorrect social security number was specified while you enter data. You could back out the entire batch of data, but it is easier and quicker to simply change the incorrect social security number.

You can do this task with IMS Database Repair Facility. Using key data, locate the incorrect social security number and make the change.

Scenario 3: Repairing duplicate ILKs in HALDB databases

After checking databases with the HD Pointer Checker utility of IMS HP Pointer Checker, you identified corrupted HALDB partition reorganization numbers, duplicate ILKs, and potentially duplicate ILKs in your HALDB databases. Such errors cannot be corrected with the standard IMS recovery methods or by database reorganization. Because such errors can cause data loss, you want to repair the databases as soon as possible.

You can fix such errors by using the HD Pointer Checker utility and the ILK Repair utility. The HD Pointer Checker utility generates repair information records that you use as input to the ILK Repair utility. All the databases that are logically related and PSINDEX databases are also repaired.