Ending a RGZPFM Operation

This document describes what can happen if RGZPFM is ended.

I started a reorganize physical file member (RGZPFM) on a file. The Display File Description command (DSPFD) does not show the number of records in the file. What happens if I end the RGZPFM command that is running?

While the file is being reorganized, the DSPFD command is not able to show some information. The record count is one of the attributes that cannot be displayed.

An initial step the RGZPFM command performs is invalidating all access paths related to the physical file member. What this means is that, if a RGZPFM command is interrupted, the file may not be available again for a period of time because the access paths are not in a valid state. The options to put the access paths back into a valid state are to restore the physical files (if access paths were saved) or wait for the system to rebuild the access paths.

Example

The RGZPFM command is started on a keyed physical file with five logical files and then is immediately interrupted after starting. All access paths are now invalid, including the access path of the physical file and the access paths of the five logical files.

The system automatically starts rebuilding the six access paths. (This is the default based on the RECOVER attribute of the file.) The EDTRBDAP command lists the access paths. The QDBSRVxx jobs rebuild the access paths at priority 51 (lower than batch). (The priority of these jobs cannot be changed.) If applications must process the files by key, those applications appear to hang, waiting for the access paths to rebuild or fail because the access paths are not in a valid state.

The following options allow you to increase the speed of the access paths rebuilds once the RGZPFM command has been interrupted:

o	Allow the QDBSRVxx jobs to finish rebuilding the access paths. Placing more memory into the base pool and decreasing CPU utilization allows the access paths to build more quickly.
o	Use the EDTRBDAP command to change the status of the access paths first to *HLD, then to *OPN. Then, submit individual jobs to open the files. This can be done using the OPNDBF command on the CMD parameter of a SBMJOB command. Opening the file for input causes the access path to be rebuilt. The access path rebuilds at the priority of the batch job.
o	Restore the physical files and access paths. If access paths were saved, restoring the physical files also causes the access paths to be restored. (There is no parameter that must be specified on the restore command.)