Where the replication of journal entries start

Attached receiver on target system

The replication of journal entries starts with the journal receiver that is currently attached to the remote journal on the target system. The journal entries are replicated from the corresponding journal receiver that is associated with the journal on the source system. The replication starts with the journal entries that follow the last journal entry that currently exists in the attached journal receiver on the target system.

The remote journal on the target system might not have an attached journal receiver. If this occurs, the journal receiver that is currently attached to the journal on the source system is created on the target system. That journal receiver is then attached to the remote journal on the target system. Then journal entries are replicated starting with the first journal entry in the journal receiver that is currently attached to the journal on the source system.

If the journal on the source system does not have an attached journal receiver, no journal entries can be replicated, and an error is returned. This is only possible in the case of a remote journal that is associated with another remote journal.

To use this option specify one of the following:

• Use the *ATTACHED special value for the Starting journal receiver (STRJRNRCV) parameter on the Change Remote Journal (CHGRMTJRN) command.
• Use the *ATTACHED special value for the Starting journal receiver (STRJRNRCV)parameter on the Change Remote Journal (CHGRMTJRN) command.

Attached receiver on source system only

The replication of journal entries starts with the journal receiver that is currently attached to the journal on the source system.

If the corresponding journal receiver exists and is attached to the remote journal on the target system, journal entries are replicated. Replication starts with the journal entries that follow the last journal entry that currently exists in the attached journal receiver on the target system. Otherwise, if the corresponding journal receiver exists but is not attached to the remote journal on the target system, no journal entries can be replicated. The system returns an error.

If the corresponding journal receiver does not exist on the target system, the journal receiver is created and attached to the remote journal on the target system. Journal entries then are replicated starting with the first journal entry in the journal receiver that is currently attached to the journal on the source system.

If the journal on the source system does not have an attached journal receiver, journal entries cannot be replicated, and the system returns an error. This is only possible in the case of a remote journal that is associated with another remote journal.

To use this option specify one of the following:

• Use the *SRCSYS special value for the Starting journal receiver (STRJRNRCV) parameter on the Change Remote Journal (CHGRMTJRN) command.
• Use attached receiver on source system only in the Activate dialog in iSeries™ Navigator.

Qualified journal receiver name

The replication of journal entries starts with the specified journal receiver name for the journal on the source system.

If the corresponding journal receiver exists and is attached to the remote journal on the target system, journal entries are replicated. Replication starts with the journal entries that follow the last journal entry that currently exists in the attached journal receiver on the target system. Otherwise, if the corresponding journal receiver exists but is not attached to the remote journal on the target system, no journal entries can be replicated. The system returns an error.

If the corresponding journal receiver does not exist on the target system, the journal receiver is created and attached to the remote journal on the target system. Journal entries then are replicated starting with the first journal entry in the specified journal receiver.

If the journal on the source system is not associated with the specified journal receiver, no journal entries can be replicated, and an error is returned.

The creation of any receiver on the target system by the change journal state processing is performed as though the receiver was being saved and restored to the target system. Therefore, the ownership of the receiver on a target system will follow the same rules as with the existing save and restore functions. If the user profile which owns the receiver on the source system is on the target system, then that profile will own the created receiver on the target system. If the user profile does not exist on the target system, then the profile QDFTOWN will own the receiver on the target system.

Additionally, information such as the audit attributes, public authority, and primary group of the source journal receiver at the time it was attached to the source journal will be incorporated into the created journal receiver on the target system. If the owner, owner's authority, public authority, primary group, or audit attributes of the source system's receiver are changed, those changes will be propagated to the target system when the next receiver is attached to the target journal. Changes made to other private authorities of the source system's receiver must be maintained separately on the target system.

If the library for the journal receiver resides in an ASP, the journal receiver will be created in that ASP. The remote journal function does not support nonlibrary ASPs for the ASP of the remote journal receiver. See Journal receiver disk pool considerations for more information.