CDC Guide for z/OS

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

Back Next

Warm Start Processing

When the Condense job is started, it checks for existing checkpoint files using the prefix specified in CHKPT_BASENAME in the CAPTPARM member pointed to by the DTLCACFG DD statement. If at least one checkpoint file is found, the Condense job warm starts. The following message is written to the PowerExchange log (DTLOG or DTLLOG
nn
if using alternative logging) for each Checkpoint data set that is found:

PWX-06038 Checkpoint file chkpt_basenameVn has time yy/mm/dd hh:mm:ss.

This message indicates the latest checkpoint time in that checkpoint file. You may also see the following message if some of the data sets defined by the CHKPT_NUM do not exist:

PWX-06365 Warning: Checkpoint file chkpt_basenameVn could not be read and was ignored: Checkpoint FILE chkpt_basenameVn Does not exist. OPEN retcodes 268/4/5896

Do not change CHKPT_NUM to a lower value and warm start Condense. This action can cause incorrect warm start processing and duplicate data being condensed. The Condense job only verifies as many checkpoint files as specified in CHKPT_NUM. For example, if the latest checkpoint is in V3 and CHKPT_NUM is changed to 3, only checkpoint files V0, V1, and V2 are checked to determine the latest checkpoint.

After the existing checkpoint file have been read and the latest checkpoint has been determined, the following message indicates which checkpoint file is being used for Condense restart:

PWX-06040 Checkpoint restart using file chkpt_basenameVn.

The capture registrations eligible for Condense are processed (as indicated by the PWX-06118 messages) and the warm start complete message is issued:

PWX-06048 Controller: Warm start complete. Tables restored from checkpoint file.

At this point in the initialization process, the Controller task starts the Command Handler and Condense subtasks of the Condense job. The restart tokens that are to be used as the starting point for data extraction from the PowerExchange Logger are echoed in the PowerExchange log with the following message:

PWX-06413 Condense: Highest Restart Token. Sequence=sequence_token_value 
PowerExchange Logger=restart_token_value

After the restart point is established, cleanup processing occurs for condense files and CDCT entries that are being expired as a result of the cold start, a checkpoint is taken to the current checkpoint file, and the initialization process is now complete. This is indicated by the following messages in the PowerExchange log:

PWX-06111 Controller: All tasks initialisation complete.
PWX-06455 Command Handler: received CAPTURE_STARTUP_COMPLETE event.

Then, the first condense operation is triggered.

When a condense operation is in progress, you can shut down the Condense job by issuing the SHUTDOWN command from the command line. The SHUTDOWN command might cause an incomplete UOW being written to the final condense file. When the Condense job is restarted, this is detected and a file switch is done when an end UOW record is encountered. The following messages are issued to indicate this has occurred:

PWX-06414 Condense: Checkpoint ERT shows incomplete UOW on previous partial Condense
PWX-06419 Condense: Doing file switch. Records=nn Reason=1st EndUOW after previous file switch Cdcts=nn CPU: TotMs=nnnnnn Diff=nnnnnn

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

Warm Start Processing

Warm Start Processing