Get information about remote journal entries

Working with the journal entries in a remote journal is essentially the same as working with the journal entries in a local journal.

The exceptions are explained in the following topics:

• File identifier considerations for working with integrated file system entries
  If you plan to replay the integrated file system operations in the remote journal to objects on the target system, and if you primed that target system with objects that were restored from the source system, then some additional considerations apply to replaying those journal entries.
• Confirmed and unconfirmed journal entries
  For a local journal, all entries are confirmed entries. There is no concept of unconfirmed entries.
• Journal entries from a remote journal with library redirection
  All journal entries that are retrieved from a remote journal will have the object names as they exist on the local system.
• Retrieve journal entries from a remote journal during the catch-up phase
  During the catch-up phase, journal entries that have been replicated to the target system can be retrieved from the remote journal.
• Remote journal considerations for retrieving journal entries when using commitment control
  Special performance related processing is done by the system when depositing entries that are associated with commitment control transactions to a local journal.
• Remote journal considerations for retrieving journal entries when using journal caching
  When you use journal caching for the local journal, the system performs special performance-related processing when it deposits journal entries.