Data recovery and integrity

 

You can specify several file processing parameters for data recovery and integrity.

• Protecting your files with journaling and commitment control
  Journaling and commitment control are the preferred methods for i5/OS^® data and transaction recovery. You can use the COMMIT parameter to protect your file with journaling and commitment control.

• Writing data and access paths to auxiliary storage
  Normally, DB2 Universal Database™ for iSeries™ determines when to write changed data and access paths from main storage to auxiliary storage. However, you can control when database changes are written to auxiliary storage.

• Checking changes to the record format description
  When a database file is opened, the system checks whether the description of the record format has been changed since the program was compiled to an extent that it cannot process the file.

• Checking the expiration date of a physical file member
  The system can check whether the data in a physical file member is still current. You can specify whether the system checks the expiration date of a physical file member using the EXPCHK parameter on the Override with Database File (OVRDBF) command.

• Preventing the job from changing data in a file
  If you want to test your program, but do not want to change data in a file that is used for the test, you can tell the system not to write (inhibit) any changes to the file that the program attempts to make. For this operation, you can use the INHWRT parameter.

 

Parent topic:

Database file processing: Runtime considerations