Database file recovery during the IPL

During the initial program load (IPL), nothing but the recovery function is active on the system.

Database file recovery during the IPL consists of the following actions:

• The listed functions that were in progress when the system ended are completed:
  • Delete file
  • Remove member
  • Rename member
  • Move object
  • Rename object
  • Change object owner
  • Change member
  • Grant authority
  • Revoke authority
  • Start journal physical file
  • Start journal access path
  • End journal physical file
  • End journal access path
  • Change journal
  • Delete journal
  • Recover SQL views
  • Remove physical file constraint
• The listed functions that were in progress when the system ended are backed out (and you must run them again):
  • Create file
  • Add member
  • Change file
  • Create journal
  • Restore journal
  • Add physical file constraint
• If the operator is doing the IPL (attended IPL), the Edit Rebuild of Access paths display appears on the operator's display. The display allows the operator to edit the RECOVER option for the files that were in use for which immediate or delayed maintenance was specified. If all access paths are valid, or the IPL is unattended, no displays appear.
• Access paths that:
  • have immediate or delayed maintenance
  • are specified for recovery during IPL (from the RECOVER option or changed by the Edit Rebuild of Access Paths display)
  • are rebuilt and a message is sent when you start journaling your access paths. Placing journal receivers in their own user auxiliary storage pool provides the best journaling performance, while helping to protect them from a disk failure.