Retrieving entries from a journal is a common practice, done for numerous purposes such as auditing changes to objects, debugging applications, and replaying journal changes. At times it is beneficial to limit the journal entries that are retrieved to only those deposited for a single object or a group of objects. For the most part, specifying objects by name on the journal entry retrieval commands and APIs is a simple matter and will return exactly what you expect. But there are also times when unexpected results occur, particularly when the objects have gone through recent changes such as moves, deletes, restores, and start or end journaling operations. Understanding how the system decides which journal entries to return is key to understanding how to use journal entry retrieval commands and APIs effectively and optimally.
The material included in this document is in DRAFT form and is provided 'as is' without warranty of any kind. IBM is not responsible for the accuracy or completeness of the material, and may update the document at any time. The final, published document may not include any, or all, of the material included herein. Client assumes all risks associated with Client's use of this document.