CDC Guide for z/OS

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

Back Next

Monitoring the PowerExchange Logger for z/OS

The PowerExchange Logger for z/OS archives active logs when they become full. You must monitor the PowerExchange Logger to ensure that the archiving process keeps pace with the data flow. If the PowerExchange Logger uses all available active log space, PowerExchange change data capture and extraction will be impacted until the PowerExchange Logger archival process makes active log space available. Specifically, PowerExchange ECCRs will be unable to record new change data and extraction operations may be unable to read captured change data.

The PowerExchange Logger issues the following message to allow you to monitor the status of the active log data sets:

PWXEDM172672I EDM Logger last active log data set is nn percent full

The PowerExchange Logger issues this message when the last available active log data set is 75 percent full, and reissues this message after each additional five percent of the remaining data set space is filled. The PowerExchange Logger retries the archive process each time it issues this message.

You should also monitor the PowerExchange Logger for other operational issues that may be unrelated to the active logs and archive log process. For example, if the PowerExchange Logger runs in a Workload Manager (WLM) service class with a lower priority than a highly-active ECCR, the Logger might delay the ECCR because it cannot write change data to the active log data sets fast enough. For more information about WLM service classes, see Using WLM Service Classes to Prioritize PowerExchange CDC Started Tasks on z/OS.

PowerExchange issues the following Write-To-Operator (WTO) messages to allow you to monitor the status of change data recording:

PWXEDM172824W EDM Change Capture waiting on [the Logger’s queue|the ECCR-to-CIC queue] since date time. Using EDM Logger logger_ID.

An ECCR issues the PWXEDM172824W message if it cannot send change data to the PowerExchange Logger because the circular queue is full. For synchronous ECCRs, the transaction or VSAM batch job that encounters the full queue waits until it can log the change data to the circular queue. For asynchronous ECCRs, the ECCR address space waits until it can log the change data to the circular queue.

PWXEDM172825W UOWs are waiting on EDM syncpoint; see EDM log

The ECCR issues the PWXEDM172825W message if the PowerExchange Logger does not respond to the ECCR within approximately 1 minute after the ECCR sends an end-UOW. This situation can occur if the PowerExchange Logger cannot keep pace with the ECCR or if a transitory PowerExchange Logger slowdown is occurring because of system issues, such as an SVC dump. The accompanying PWXEDM172826W message includes the UOW ID.

For synchronous ECCRs, the transaction or VSAM batch job waits until the PowerExchange Logger indicates that the end-UOW has been logged to the active log data set. For asynchronous ECCRs, the ECCR address space waits until the end-UOW has been logged.

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

Monitoring the PowerExchange Logger for z/OS

Monitoring the PowerExchange Logger for z/OS