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):||11 June 2008|
|PDF File Size:||2.41 Mb|
|ePub File Size:||5.22 Mb|
|Price:||Free* [*Free Regsitration Required]|
Logical file journaling The system automatically starts journaling logical files built over a journaled physical file when it finds a need to. Starting journaling This topic provides information about journalint to start journaling for all object types. 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.
When using save-while-active, updating the history for the object is not needed for verification when applying aa400 removing journaled changes. The result is journal entries recording things like authority changes for logical files.
The start journal command must obtain an exclusive lock on the object. After you have created the journal and journal receiver, you can start journaling. However, for database physical files and integrated file system objects, you can start journaling even if an object is open. This is referred to as covert journaling. This topic provides information about how to start journaling for all object types.
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 data queue.
For the other save related commands, the default value is to preserve the update history. The ss400 links provide instructions to start journaling for each object type: Starting and ending journaling and changing journaling attributes.
Normally, only the definition of a data queue is saved, not its contents. Journal access paths After you have started journaling for physical files, you can set up explicit journaling of access paths.
If you saved the object using the SAV command, the default value is to not preserve the update history. In this case, information is saved on media with the object, and restored when the object is restored.
Any access path associated with the logical file is not covertly journaled. The recommended procedure for starting journaling is: Automatically starting journaling You can automatically journal objects created into libraries or directories. If you are not using the save-while-active function, 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. This extra information jourbaling the last save information for applying and removing journaled changes.
The maximum number of objects that can be associated with one journal is either or 10 Journaling libraries Allows you to start journaling changes to a library and automatically journal any objects created, moved, or restored into a library.
When journaling has been started for an object, the system writes journal entries for all changes to the object. The recommended procedure for starting journaling is:.
You can also have all objects ax400 within a subdirectory start journaling automatically without having to be broken up when you reach the limit. Journal DB2 Multisystem jourhaling 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 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.