CDC Guide for z/OS

10.4.1
- 10.5.8
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.0 HotFix 1
- 10.4.0

Back Next

PowerExchange Logger Configuration Considerations

Before you begin configuration, review the following considerations related to PowerExchange Logger for z/OS configuration.

A PowerExchange Logger can log data from multiple ECCRs that operate on the same z/OS system. By using Post-Log Merge, you can access changes from multiple z/OS systems as if they were stored in a single PowerExchange Logger environment.

If you use multiple PowerExchange Loggers, you need a copy of the EDMSDIR default options module for each PowerExchange Logger instance. Because you cannot rename the EDMSDIR module, you must allocate a separate USERLIB for each copy of EDMSDIR. To reduce the chance of data loss, use dual active log data sets and dual archive log data sets.

If you reinitialize the PowerExchange Logger after you start capturing changes, the RBA is reset to 0 and you lose all of the changes that have been captured but not yet applied.

You must reinitialize the PowerExchange processes that consume data from the PowerExchange Logger. If you restart these processes in the normal manner, PowerExchange uses the last-read PowerExchange Logger RBA to generate the restart point. However, reinitialization of the PowerExchange Logger invalidates the last-read RBA.

On a z/OS version 1.12 system, PowerExchange Logger active log data sets cannot be larger than 4 GB.

Also, you must apply IBM APAR OA34369. Otherwise, the PowerExchange Logger might abend when it tries to use data-in-virtual (DIV) services to access its log data sets.

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

PowerExchange Logger Configuration Considerations

PowerExchange Logger Configuration Considerations