CDC Guide for z/OS

10.4.0 HotFix 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.1
- 10.4.0

Back Next

Post-Log Merge System Requirements

The collection of all of the member Loggers is referred to as the Post-Log Merge group. To use Post-Log Merge to merge logged data from multiple Loggers running on multiple MVS systems, the following criteria must be met:

All of the MVS systems running member Loggers in the Post-Log Merge group must be a part of the same base sysplex (parallel sysplex is not required).

There must be sufficient available XCF groups to support the Post-Log Merge environment. Each member Logger creates an XCF group. The Post-Log Merge job creates an XCF group, which is named by using the PowerExchange Logger ID value. All member Loggers join the Post-Log Merge XCF group.

Therefore, the total number of XCF groups that PowerExchange requires is the sum of all of the member Loggers plus one for the Post-Log Merge XCF group. For example, if you have three member Loggers on three MVS systems, there are four XCF groups created.

Each PowerExchange Logger XCF group name must be unique within the sysplex. PowerExchange creates the name for the member Logger XCF group by appending the SMF ID of the MVS system to PowerExchange Logger ID value from the LOGGER_NAME parameter in the EDMUPARM module options.

If the SMF ID value for the MVS system on which a member Logger runs is not unique within the Post-Log Merge group, you can specify a unique value to override the SMF ID in the PARM parameter of the EXEC JCL card for the member Logger.

The Logger emergency restart data sets (ERDS
nn
) and the active log data sets for all member Loggers in the Post-Log Merge group must be on shared DASD.

If the archive logs are on DASD, they must also be on shared DASD. If the archive logs are on TAPE, the tapes must be accessible to the system on which the Post-Log Merge job runs. This applies to all member Loggers in the Post-Log Merge group.

All PowerExchange MVS capture sources that support multi-system access and update can utilize Post-Log Merge. You must run the appropriate capture source ECCR (along with the Agent and the Logger) on each MVS system for which you want the Post-Log Merge job to merged changes.

DB2 data sharing does not require Post-Log Merge. The DB2 IFI 306 interface calls utilized by the DB2 ECCR result in all changes being captured from a database on any system in the data sharing group. Running multiple DB2 ECCRs in a DB2 data sharing group results in changes being captured numerous times.

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

Post-Log Merge System Requirements

Post-Log Merge System Requirements