AS400 JOURNALING PDF
This topic provides information about how to start journaling for all object types. Journaling is the primary mechanism used by logical software i customer since it was the good old AS/ and came in a white box, you are. It’s surprising how few AS/ shops actually implement journaling. Even shops with transaction-logging requirements frequently miss out on.
|Published (Last):||13 March 2008|
|PDF File Size:||16.91 Mb|
|ePub File Size:||18.25 Mb|
|Price:||Free* [*Free Regsitration Required]|
If you are not using the save-while-active journalng, it is highly recommended that you update the history for the object when you save it so that processing for applying and removing journaled changes will have the best information for verification. The recommended procedure for starting journaling is:.
You can also have all objects created within a subdirectory start journaling automatically without having to be broken up when you reach the limit.
Starting and ending journaling and changing journaling attributes. This is referred to as covert journaling.
Journal access paths After you have started journaling for physical files, you can set up explicit journaling of access paths.
The start journal command must obtain an exclusive lock on the object. The option of setting the journal object limit to 10 simplifies journaling because there are fewer journwling to manage, but allows for less parallelism during IPL and disaster recovery.
Journaling libraries Allows you to start journaling changes to a library and automatically journal any objects created, moved, or restored into a library. In this case, information is saved on media with the object, and restored when the object is restored. Starting journaling This topic provides information about how to start journaling for all object types. The result is journal entries recording things like authority changes for logical files.
The recommended procedure for starting journaling is: Journal DB2 Multisystem jourjaling When you successfully start journaling on a distributed file, the system distributes the start journal request to the other servers in the node group.
The following links provide instructions to start journaling for each object type: Logical file journaling The system automatically starts journaling logical files built over a journaled physical file when it finds a need to.
Journaling database physical files tables When you start journaling a physical file tableyou specify whether you want after-images saved, or both before-images and after-images. This topic provides information about how to start journaling for all object types.
For the other save related commands, the default value is to preserve the update history. However, for database physical files and integrated file system objects, you can start journaling journzling if an object is open.
When journaling has been started for an object, the system writes journal entries for all changes to the object. This extra information provides the last save information for applying and removing journaled changes. Normally, only the definition of a data queue jojrnaling saved, not its contents. The maximum number of objects that can be associated with journaking journal is either or 10 When using save-while-active, updating the history for the object is not needed for verification when applying and removing journaled changes.
Automatically starting journaling You can automatically journal objects created into libraries or directories. If you saved the object using the SAV command, the default value is to not preserve the update history.
After you have created the journal and journal receiver, you can start journaling. Journaling data areas and data queues When you start journaling for a data area or a data queue, the system writes journal entries for all changes to the data area or nournaling queue. Any access path associated with the logical file is not covertly journaled.