Saving database files

 

This information describes what the system does when you save a database file.

Use the SAVOBJ command to save individual database files. You can use the FILEMBR (file member) parameter to save:

• A list of members from one database file.

• The same group of members from multiple files.

Here is what the system does when you save a database file:

---

Table 1. Saving database files

Type of File	What is saved
Physical file, TYPE(*DATA), keyed access path1	Description, data, access path
Physical file, TYPE(*DATA), access path not keyed	Description, data
Physical file, TYPE(*SRC), keyed access path	Description, data
Logical file2	Description
1 The following types of access paths are included as keyed access paths: keyed access paths, primary key constraints, unique constraints, referential constraints. 2 You can save the access path for a logical file by saving the associated physical files using the SAVLIB, SAVOBJ, or SAVCHGOBJ command and specify the ACCPTH parameter..

---

The description for a file may include the following:

• Definitions of triggers and the programs that are associated with the file, but not the programs themselves. You must save the programs separately.

• Definitions of any constraints for the file.

Special considerations apply when you restore a file that has trigger programs or constraints defined. You can find additional information about how the system restores files with triggers and files with referential constraints in the Backup and Recovery book.

• Saving access paths
  When you restore a database file, but you did not save the access path to the database, the system rebuilds the access path. You can significantly reduce the amount of time it takes you to recover if you save the access paths. However, the process that saves access paths increases the time for the save operation and the amount of media that you use.

• Saving files with referential constraints
  Referential constraints link multiple files together in a network, similar to the network for access paths. You might think of this as a relationship network. If possible, you should save all the files in a relationship network in a single save operation.

 

Parent topic:

Saving user data in your system

Related concepts
Saving journaled objects

Related information
SAVOBJ command