Database file recovery after the IPL

 

This recovery of database files runs after the initial program load (IPL) is completed. Interactive and batch jobs can continue with the recovery.

The database file recovery after the IPL consists of the following actions:

• The access paths for immediate or delayed maintenance files that specify recovery after IPL are rebuilt.

• The system history log receives messages that indicate the success or failure of the rebuild operations.

• After IPL completion, use the Edit Rebuilt of Access Paths (EDTRBDAP) command to order the rebuilding of access paths.

• After IPL completion, the Edit Check Pending Constraints (EDTCPCST) command displays a list of the physical file constraints in check pending. This command specifies the verification sequence of the check pending constraints.

If you are not using journaling for a file, records might or might not exist after IPL recovery:

• For added records, if after the IPL recovery the Nth record added exists, then all records added preceding N also exist.

• For updated and deleted records, if the update or delete operation on the Nth record is present after the IPL recovery, there is no guarantee that the records updated or deleted prior to the Nth record are also present in the database.

• For REUSEFLT(*YES), records added are treated as updates, and these records might not exist after IPL recovery.

 

Parent topic:

Database recovery process after an abnormal system end

 

Related reference

Edit Rebuild of Access Paths (EDTRBDAP) command
Edit Check Pending Constraints (EDTCPCST) command