When you execute the frozen update command, HiRDB files with data pages that are entirely full (all pages are allocated) in a user LOB RDAREA are placed in frozen update status. Data in a HiRDB file that has been placed in frozen update status cannot be updated or deleted. Figure 7-6 provides an overview of frozen update command processing.

Figure 7-6 Overview of frozen update command processing

Explanation

• A user LOB RDAREA exists that contains HiRDB files 1 through 4. All data pages in HiRDB files 2 and 3 are full.
• Executing the frozen update command on this user LOB RDAREA places HiRDB files 2 and 3 into frozen update status. HiRDB files that are in frozen update status are indicated in the KFPH27024-I message.
• HiRDB files 1 and 4 are placed in permit update status.

Figure 7-7 shows how to use the frozen backup command to make backups.

Figure 7-7 How to use the frozen update command to make backups

Explanation

The frozen update command is executed before the backup is made. As a result, HiRDB files 2 and 3 are placed in frozen update status.

1. The first time the backup is made, a backup is made of all HiRDB files (HiRDB files 1 through 4).
2. Because HiRDB files 2 and 3 are in frozen update status, their contents do not change after the first time the backup is made. Therefore, the next time a backup is made, HiRDB files 2 and 3 do not need to be backed up. Only HiRDB files 1 and 4 are backed up.

Remark

Because the first HiRDB file (HiRDB file 1 in Figure 7-7) contains a management record, even if the data area becomes full, the file is still written to on a regular basis. Consequently, backups are always made of the first HiRDB file.