Integrated auxiliary utilities usage

IMS Database Recovery Facility operates with the integrated auxiliary utilities under the listed constraints.

IMS High Performance Image Copy

Used for database image copy generation, including incremental image copy (ICR). Taking image copies is a usual part of backup and recovery procedures.

Use the IC keyword of the ADD command to take an IC of a recovered database data set, including those in a CAGROUP or RECOVGRP. Only IMS High Performance Image Copy image copies are generated.

The following types of image copies are not generated:

• IMS Standard Image Copy Utility image copies
• IMS Online Image Copy Utility image copies
• IMS Image Copy 2 Utility image copies
• IMS HP Image Copy FlashCopy image copies

IMS utility DFSPREC0

Used for rebuilding HALDB partitions PHIDAM primary indexes and ILDS data sets.

These entities are not recoverable and DFSPREC0 must be used to rebuild them. Use the HALDB keyword of the UTILGBL control statement to activate DFSPREC0.

See the next topic, Rebuilding indexes and ILDSs.

Build Index function of FPA

Used for rebuilding Fast Path secondary indexes.

Use the IB keyword of the ADD command or the BLD_SECONDARY keyword on the UTILGBL control statement to activate the Build Index function of FPA. This is useful in cases where the indexes are not recoverable or not marked as recoverable in the RECONs.

IMS Index Builder

Used for rebuilding Full Function primary indexes and all secondary indexes, including those of HALDB partitions.

Use the IB keyword of the ADD command or the BLD_PRIMARY and BLD_SECONDARY keywords on the UTILGBL control statement to activate IMS Index Builder. This is useful in cases where the indexes are not recoverable or not marked as recoverable in the RECONs.

For more information, see Rebuilding indexes and ILDSs.

IMS High Performance Pointer Checker and IMS Fast Path Basic Tools DEDB Pointer Checker

Used for hash pointer checking of full function databases and fast path databases, respectively. These ensure the integrity of the recovered database data sets.

Use the PC keyword of the ADD command to activate hash pointer checking. Ensure that all logically-related data sets are available to Pointer Checker by including the PC keyword on the corresponding ADD commands; otherwise, Pointer Checker returns multiple pointer errors to the MAS.

However, this might be acceptable for your purposes; for example, if you only want the Free Space Report from Pointer Checker. Note that Pointer Checker does not allow for hash pointer checking of HALDB primary indexes or ILDS data sets and therefore is not called, even if they are rebuilt by DFSPREC0 as part of the recovery.

IMS Library Integrity Utilities

Used for verifying the database descriptor (DBD) in the DBDLIB used for recovery and any invoked integrated auxiliary utilities.

The DBD in the DBDLIB is the same as the DBD used for building the database. This prevents database corruption due to recovering a database using the wrong DBD, such as a DBD that is used for application testing or one that is outdated.

IMS Index Builder processing, DFSPREC0 processing, or processing for the Build Index function of FPA is invoked only after database recovery is complete because the entirely recovered database is required in order to rebuild the indexes or ILDSs.

You need only rebuild indexes or ILDSs if the media containing them fails or if a database is recovered to a particular time stamp (either PITR or TSR). This means that all indexes do not need to be rebuilt for all recoveries.

Image copies of indexes are taken only when the indexes are marked recoverable in the RECONs. If your installation chooses to rebuild indexes after database recovery, then taking an image copy of an index is not necessary.

For integrated auxiliary utility processing, additional JCL procedures must be defined in the procedure library. See the installed SFRXSAMP library for sample JCL procedures and instructions for their definition.