Manage database files

These topics discuss how to maintain control of database files on your system by managing the files, their descriptions and attributes. Information about how to maintain control over your data to protect it from loss, how to ensure data integrity with constraints, and how to set up trigger events when the data changes is included.

• Basic operations for managing database files
  These topics describe two basic operations for managing database files: copying a file and moving a file.
• Manage database members
  These topics describe the basic operations for managing database file members. Member operations unique to physical files are also included.
• Use database attribute and cross-reference information
  The iSeries™ integrated database provides file attribute and cross-reference information.
• Change database file descriptions and attributes
  These topics discuss how to change the database file descriptions and attributes. Considerations for changing fields in a file description are also included.
• Recover and restore your database
  These topics discuss the iSeries™ functions of recovering or restoring your database after the system loses data.
• Use source files
  These topics describe how to enter and maintain data in a source file and how to use that source file to create another object (for example, a file or program) on the system.
• Control the integrity of your database with constraints
  A constraint is a restriction or limitation placed on a file to ensure that the data in your database remains consistent as you add, change, and remove records. These topics describe how to use constraints to ensure data consistency.
• Ensure data integrity with referential constraints
  These topics discuss how to use referential constraints in your database to ensure that it contains only valid data.
• Trigger automatic events in your database
  A trigger is a set of actions that run automatically when a specified change or read operation is performed on a specified database file. On iSeries™, you define a set of trigger actions in any supported high-level language.
• Database distribution
  DB2^® Multisystem, a separately priced feature, provides a simple and direct method of distributing a database file over multiple systems in a loosely-coupled environment.