The library refresh feature does not support remote journals. All of the libraries in the request must be journaled to the same local user journal.

You must use PowerExchange Client for PowerCenter (PWXPC) connections to PowerCenter. The refresh feature does not support ODBC connections.

The library refresh feature does not support PowerExchange Condense or remote logging of data to a PowerExchange Logger for Linux, UNIX, and Windows instance.

A refresh request for added or deleted libraries applies to all current PowerExchange capture processes that use the user journal with the entry for the add library or delete library operation.

Usually, an *ADDLIB or *DLTLIB refresh request does not significantly degrade capture processing and does not slow or stop PowerCenter workflow processing. However, if PowerExchange is behind in reading the journal, the refresh request might not be processed in a timely manner and could disrupt other planned activity.

PowerExchange validates the library names in the refresh request to ensure that they exist and are not repeated in the same request. However, PowerExchange does not validate the journaled table (file) instances in these libraries.

Ensure that the journal entry type codes that PowerExchange uses to mark an add library (*ADDLIB) request or a delete library (*DLTLIB) request are not used by any other application. If the default values I1 and I2 are used by another application, add the AS400USRJRNCODE statement in the DBMOVER member to define unique journal entry type codes for refresh operations.

Refresh requests do not advance the restart point for extraction processing. If a data extraction stops between the time the refresh request is issued and the arrival of the next UOW of interest, or if the restart tokens are advanced based on the RSTRADV parameter in the UOWC CAPI_CONNECTION statement, the refresh transaction occurs beyond the last restart point and will be processed again when the extraction restarts. This behavior can be a problem on test systems in particular.

If you issue a delete library (*DLTLIB) request while a CDC real-time session is running, PowerExchange refreshes the CDC interest list and blocks the deleted libraries from capture processing for the current CDC session run only. The next time you run the CDC session, the library changes that were in the refresh request are no longer honored. The new CDC session processes all of the libraries in its current CDC interest list.

For an add library (*ADDLIB) request, PowerExchange writes audit message PWX-06815 for the add library request twice. The first time, the PWX-06815 message includes an asterisk (*) next to the library names to alert you that these libraries are included in a new *ADDLIB refresh request and will be added to CDC processing. The second time, the PWX-06815 message reports only the requested library names.

If you delete multiple i5/OS libraries that contain DB2 for i5/OS table instances that have the same structure and use the same journal and then add back these same libraries, the SNDPWXJRNE request for the add-library operation does not update the CDC interest list and the warning message PWX-06817 is issued.