When PowerExchange runs on the same system as the DB2 source tables, PowerExchange can validate that a registered source table is journaled to a specific journal. However, when PowerExchange runs on a remote system, PowerExchange cannot validate the association between a source table and a remote journal. In this case, you should verify that a source table is correctly associated with a remote journal. On the local system where the table resides, enter the WRKJRNA command and select the option to view remote journal information.

When you create capture registrations for the DB2 source tables or perform database row tests in the PowerExchange Navigator, select the node name for the remote system in the

Location

field.

You can install and run the PowerExchange Listener on the local system as well as on the remote system to access metadata for the DB2 source tables when you create capture registrations or perform database row tests. However, running the PowerExchange Listener on the local system is not necessary because the PowerExchange Listener on the remote system can access metadata for the source tables on the local system.

PowerExchange supports i5/OS library redirection so that you can use names for the remote journals and journal libraries that are different from those of the associated local journals and journal receivers, if you prefer.

The remote journals can be in a cascade configuration in which one remote journal writes to another remote journal, or in a broadcast configuration in which a local journal writes to multiple remote journals.