CDC Guide for z/OS

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

Back Next

Configuring Post-Log Merge

The following steps detail the necessary changes required to the installation to create a Post-Log Merge environment.

To configure post-log merge:

Define unique Logger data sets for each system.

Members SETUPVSM and SETUPCC2 in RUNLIB defines the Logger data sets. Ensure that the Logger active logs and ERDS data sets defined are unique for each Logger that are a part of the Post-Log Merge group.

Ensure a unique USERLIB data set is created.

Member SETUPCC1 in RUNLIB creates the USERLIB data set. The default data sets name created is &HLQ..&LOGGER..USERLIB. This pattern might not create a unique USERLIB data set for each Logger. If necessary, change this name to ensure it is unique.

RUNLIB contains many members that refer to this USERLIB and they also need to be changed as well.

Create an EDMSDIR module for each USERLIB data set.

Member SETUPAGT in RUNLIB creates the EDMSDIR member in USERLIB. This member contains specifications that should be reviewed and changed where required:

LOGRGRP= must be changed from N (no Post-Log Merge) to Y (Post-Log Merge)

LOGGER= must be the Logger name. This Logger name must be the same for all member Loggers in the Post-Log Merge group.

Create a unique EDMUPARM for each USERLIB data set.

Member SETUPCC2 in RUNLIB creates the EDMUPARM member in USERLIB. This member contains specifications that should be reviewed and changed where required:

SUFFIX= in SYSTEM_OPTIONS must be a unique number for each member Logger of the Post-Log Merge group

LOGGER_NAME= in SYSTEM_OPTIONS must be the Logger name. This Logger name must be the same for all member Loggers in the Post-Log Merge group.

PREFIX_COPY1= and PREFIX_COPY2= in ARCHIVE_OPTIONS must be specify unique high-level qualifiers (HLQ) for the archive logs of each member Logger of the Post-Log Merge group.

TIME_CHKPT_FREQ= in SYSTEM_OPTIONS should be reviewed and changed if necessary.

TIMER_INTERVAL= in SYSTEM_OPTIONS should be reviewed and changed if necessary.

In environments with member Loggers that are occasional less active than others, you need to carefully consider the values specified for TIME_CHKPT_FREQ= and TIMER_INTERVAL=. Lower values reduce extraction latency in a Post-Log Merge environment.

Customize the PowerExchange Logger JCL, as necessary.

If your MVS systems do not have unique SMF IDs, update the PowerExchange Logger JCL for those systems to override the non-unique SMF ID with a unique value.

This completes the additional installation customization required for Post-Log Merge.

Post-Log Merge Configuration

SYSTEM_OPTIONS Parameters

Customizing the PowerExchange Logger JCL

Performance Considerations

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal