Plan for remote journals

The following topics provide detailed information for planning to set up remote journals:

• Journals that are good candidates for remote journal management
  Journals that you are currently replicating, or that you plan to replicate, in their entirety to one or more systems, are excellent candidates for the remote journal function.
• Synchronous and asynchronous delivery mode for remote journals
  The terms asynchronously maintained and synchronously maintained both describe a remote journal function delivery mode for journal entry replication.
• Communications protocol and delivery mode for remote journals
  The greater the volume of traffic, that is the higher the rate of journal entry deposits, the faster communications method you must choose. If your traffic is minimal, then a slower communications method can be adequate.
• Where the replication of journal entries start
  When you specify a journal receiver for remote journaling, you are specifying where the replication of journal entries will start.
• Factors that affect remote journal performance
  There are two main performance objectives for the remote journal function. To provide a timely delivery of journal entries to a target system and to minimize impacts to the journaling throughput on the source system.
• Remote journals and auxiliary storage
  Auxiliary storage will be required on both the source and target systems. The amount that is required will be about the same on both systems.
• Journal receiver disk pool considerations
  The receiver configuration is the disk pool the receiver resides in, and how the data for the receiver is spread across the disk arms within that disk pool.
• Remote journals and main storage
  Providing greater amounts of main storage in the *BASE main storage pool on the source system might improve remote journal performance. Improvements are most likely in environments with one or more asynchronously maintained remote journals.