Ending journaling

This topic provides information about how to end journaling and why ending journaling might be necessary.

You may need to end journaling for several reasons:

If a journal is damaged and you need to delete it, you must first end journaling for all objects assigned to the journal.
In some situations, you might want to end journaling before running a large batch application, if that application has exclusive use of the object. This is done either to improve the speed of the batch application or to reduce the auxiliary storage needed for the journal receiver. If you do this, use this method:
1. End journaling for the objects.
2. If journaling physical files save them specifying ACCPTH(*YES).
3. If journaling other object types, save them.
4. Run the batch application.
5. Start journaling for the objects.
6. Save the physical files, specifying ACCPTH(*YES).
7. Save the other journaled objects.

To end journaling, proceed as follows:

End journaling for access paths with the End Journal Access Path (ENDJRNAP) command
With IBM® Navigator for i, connect to the system with the object that you want stop journaling.
1. Expand Journal Management.
2. Select Set Database/Library to use with Journal Tasks and specify the database and library that contain the object you want to end journaling for.
3. Select Journals.
4. Select the journal to which the object is journaled and the Show Journaled Objects action.
5. Select the correct tab for the object type of the object you want to end journaling for.
6. Select the object and the End Journaling action.

Or, use the following commands or API to end journaling:

End Journal Library (ENDJRNLIB) command for libraries
End Journal Access Path (ENDJRNAP) command for access paths
End Journal Physical File (ENDJRNPF) command for database files
End Journal (ENDJRN) command for integrated file system objects
End Journal Object (ENDJRNOBJ) command for other objects
End Journal (QjoEndJournal) API for integrated file system objects, data areas, and data queues.

You must end journaling for any access paths based on a physical file before you can end journaling for the physical file.

In the following cases, the system implicitly ends journaling:

When you delete an object, journaling is ended for the object.
When you remove a physical file member, journaling is ended for the member.
When you remove a physical file member, journaling is ended for any access paths associated with the member unless an access path is shared and journaled by another file member.
When you delete a file, journaling is ended for any access paths associated with the file unless an access path is shared and journaled by another file.

When you successfully end journaling on a distributed file, the system distributes the end journal request to the other systems in the node group. All systems are attempted even if there is a failure at any one system. Once journaling is ended on a system in the node group, it stays ended even if there is a failure at any of the other systems.

Even if a distributed file is not locally journaled, and if you specify the file name and the journal name on the ENDJRNPF command, the system will still attempt to distribute the end-journal request to the other systems in the file node group.