How the system chooses access paths to protect

The system periodically examines access path exposure and estimates how long it would take to rebuild all the exposed access paths. If the rebuild time exceeds your target recovery times for access paths, the system selects additional access paths for protection.

An access path is exposed when the access path has changed because records have been added or deleted or because a key field has changed, and those changes have not yet been written to the disk. The system periodically examines access path exposure and estimates the time required to rebuild all the exposed access paths. If the rebuild time exceeds your target recovery times for access paths, the system selects additional access paths for protection. The system can also remove access paths from protection if the estimated time for rebuilding access paths consistently falls below your target recovery times for access paths. The recover attribute of a file is not used in determining whether to protect access paths.

Some access paths are not eligible for protection by SMAPP:

• A file that specifies MAINT(*REBLD).
• An access path that is already explicitly journaled.
• An access path in the QTEMP library.
• An access path whose underlying physical files are journaled to different journals.
• A file journaled to a journal in standby state.
• Some access paths that use an international component for unicode (ICU) sort sequence table and aggregate encoded vector indexes.

You can use the Display Recovery for Access Paths (DSPRCYAP) command to see a list of access paths that are not eligible for SMAPP.