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

Continuous Mode

On a z/OS system, a Condense job in continuous mode can run for a long period, such as 24x7. After each condense cycle, the Condense subtask sleeps until it is triggered again.

The next condense cycle is triggered by one of the following events:

The number of minutes defined by the NO_DATA_WAIT parameter elapses.

A CONDENSE command is issued from the command line, or a pwxcmd condense command is issued from a remote Linux, UNIX, or Windows system.

A FILESWITCH command is issued from the command line, or a pwxcmd fileswitch command is issued from a remote Linux, UNIX, or Window system.

A SHUTCOND command is issued from the command line, or a pwxcmd shutcond command is issued from a remote Linux, UNIX, or Windows system.

In continuous mode, the Condense job does not shut down automatically. To shut down the Condense job down, you must issue the SHUTDOWN or SHUTCOND command.

PowerExchange performs a file switch when the file switch criteria defined by the FILE_SWITCH_CRIT and FILE_SWITCH_VAL parameters are met or when you issue a FILESWITCH command. File switch processing closes open condense files if they contain data and then opens a new set of condense files for new changes. After a file switch, the closed condense files become available to change data extraction processes.

A file switch does not occur if the current condense file does not contains data. PowerExchange next tries the file switch when the FILE_SWITCH_CRIT and FILE_SWITCH_VAL criteria are met. If the condense file still does not contain data, PowerExchange Condense continues retrying the file switch at the set intervals until data is available.

The following sample message output shows the Condense task reaching the end of log and then starting the wait interval of 5 minutes:

PWX-06455 Command Handler: received CAPTURE_STARTUP_COMPLETE event.
PWX-06417 Condense: Start to Condense because initialisation complete
PWX-09957 CAPI i/f: Read times out after 60 seconds
PWX-06419 Condense: Doing file switch. Records=658 Reason=Records criteria met Cdcts=48 
          CPU: TotMs=232640 Diff=232640
PWX-06418 Condense: Closed file ABCDEF1.v101.I.CND.CP160520.T2039001
PWX-06136 Checkpoint taken to file=ABCDEF1.v101.I.CHKPTV1 time=16/05/20 20:39:46
PWX-06420 Condense: Checkpoint done. Sequence=0000000AE744000000000000000AE74400000000 
          PowerExchange Logger=E2C2F2D340400000000015E200000000
PWX-06419 Condense: Doing file switch. Records=502 Reason=Records criteria met Cdcts=58 
          CPU: TotMs=488039 Diff=255399
PWX-06418 Condense: Closed file ABCDEF1.v101.I.CND.CP160520.T2039002
PWX-06136 Checkpoint taken to file=ABCDEF1.v101.I.CHKPTV2 time=16/05/20 20:39:48
PWX-06420 Condense: Checkpoint done. Sequence=000000101BE800000000000000101BE800000000 
          PowerExchange Logger=E2C2F2D340400000000015E200000000
PWX-09967 CAPI i/f: End of log for time 16/05/20 20:39:41 reached
PWX-06415 Condense: Condense completed. Total Records=2476, Data=2314, UOWs =118
PWX-06421 Condense: 16/05/20 20:40:53 Starting wait on commands for 5 minute

Key messages in this example are:

Message PWX-06420 indicates that PowerExchange Condense processed changes and has taken a checkpoint.

Message PWX-06415 indicates that the condense cycle completed with the reported processing statistics.

Message PWX-06421 indicates that PowerExchange Condense is starting the NO_DATA_WAIT interval of 5 minutes.

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

Continuous Mode

Continuous Mode