Specifying the access path recovery (RECOVER) parameter
The RECOVER parameter specifies when changed access paths that are not journaled or forced to auxiliary storage are rebuilt after the system failure. You can use the RECOVER parameter on the following commands to specify when the access path is to be rebuilt:
- Create Physical File (CRTPF)
- Create Logical File (CRTLF)
- Create Source Physical File (CRTSRCPF)
Access paths are rebuilt during the initial program load (IPL), after the IPL, or when a file is opened.
Table 1 shows your choices for possible combinations of duplicate key and maintenance options.
| With this duplicate key option | And this maintenance option | Your recovery options are |
|---|---|---|
| Unique | Immediate | Rebuild during the IPL (*IPL) Rebuild after the IPL (*AFTIPL, default) Do not rebuild at IPL, wait for first open (*NO) |
| Not unique | Immediate or delayed | Rebuild during the IPL (*IPL) Rebuild after the IPL (*AFTIPL) Do not rebuild at IPL, wait for first open (*NO, default) |
| Not unique | Rebuild | Do not rebuild at IPL, wait for first open (*NO, default) |
RECOVER parameter tip
A list of files with access paths that need to be recovered is shown on the Edit Rebuild of Access Paths display during the next IPL if the IPL is in manual mode. You can edit the original recovery option for the file by selecting the desired option on the display. After the IPL is complete, you can use the Edit Rebuild of Access Paths (EDTRBDAP) command to set the sequence in which access paths are rebuilt. If the IPL is unattended, the Edit Rebuild of Access Paths display is not shown and the access paths are rebuilt in the order determined by the RECOVER parameter. You only see the *AFTIPL and *NO (open) access paths.
Parent topic:
Specifying database file and member attributes
Related concepts
Recovering and restoring your database
