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):||19 March 2010|
|PDF File Size:||11.95 Mb|
|ePub File Size:||5.15 Mb|
|Price:||Free* [*Free Regsitration Required]|
This topic provides information about how to start journaling for all object types. After you have created the journal and journal receiver, you can start journaling.
When journaling has been started for an object, the system writes journal entries for all changes to the object. The start journal command must obtain an exclusive lock on the object. However, for database physical files and integrated file system objects, you can start journaling even if an object is open. The recommended procedure for starting journaling mournaling.
If you are not using the save-while-active ae400, 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. If you saved the object using the SAV command, the default value is to not preserve the update history.
For the other save related commands, the default value is to preserve the update history. When using save-while-active, updating the journaoing for the object is not needed for verification when applying and removing journaled changes.
In this case, information is saved on media with the object, and restored when the object is restored.
This extra information provides the last save information for applying and removing journaled changes. Normally, only the definition of a data queue is saved, not its contents.
The maximum number of objects that can be associated with one journal is either or 10 The option of setting the journal object limit to 10 simplifies journaling because there are fewer journals to manage, but allows for less parallelism during IPL and disaster recovery. You can also have all objects created within a subdirectory start journaling automatically without journalinf to be broken up when you reach the limit.
Starting journaling This topic provides information about how to start journaling for all object types. The recommended procedure for starting journaling is: The following links provide instructions to start journaling for each object type: Journaling libraries Allows you to start journaling changes to a library and automatically journal any objects created, moved, or restored into a library.
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. Journal DB2 Multisystem files When you successfully start journaling on a distributed file, the system distributes the start journal request to the other servers in the node group.
Logical file journaling The system automatically starts journaling logical files built over a journaled physical file when it finds a need to. This is referred to as covert journaling. The result is journal entries recording things like authority changes for logical files.
Any access path associated with the logical file is not covertly journaled. Journal access paths After you have started journaling for physical files, you can set up explicit journaling of access paths.
Journaling data areas and data queues Aa400 you start journaling for a data area or a data queue, the system writes journal entries for all changes to the data area or data queue. Automatically starting journaling You can automatically journal objects created into libraries or directories. Starting and ending journaling and changing journaling attributes.