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

Cold Start Processing

When you start the Condense job, it checks for existing checkpoint files that have the high-level qualifier that is specified by the CHKPT_BASENAME parameter in the CAPTPARM member.

The DTLCACFG DD statement points to the CAPTPARM member.

If the Condense job does not find a checkpoint file, it cold starts and issues the following Write-To-Operator-with-Reply (WTOR) message:

*nn PWX06101A No checkpoint files, cold start from specified restart point restart_point (Y/N)

To continue with the cold start, reply Y to the PWX06101A message. The Condense job then issues the following WTOR message to indicate that the request to cold start was accepted:

PWX06103I Cold Start accepted

To cancel the cold start, reply N to PWX06101A message. The Condense job ends immediately with the following message:

PWX06104W Cold Start declined

The Condense job writes messages to the PowerExchange DTLLOG member of the LOG file in the PowerExchange datalib library, by default. If alternative logging is enabled, Condense writes messages to a DTLLOGnn log member in the JOBjob_number file in the datalib library.

For each checkpoint file, the Condense job writes the following message to the PowerExchange message log:

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

This message indicates that the Condense job ignored the specified checkpoint file because it does not exist.

The point from which the Condense job starts getting change data from the PowerExchange Logger depends on the RESTART_TOKEN and SEQUENCE_TOKEN parameters in CAPTPARM member. Based on the values of these parameters, the following processing occurs:

If the RESTART_TOKEN and SEQUENCE_TOKEN parameters are not present in the CAPTPARM member, PowerExchange Condense starts from the current end-of-log position in the PowerExchange Logger logs.

If the RESTART_TOKEN and SEQUENCE_TOKEN parameters are set to all zeroes, PowerExchange Condense starts from the earliest available point in the PowerExchange Logger log files. In a Post-Log Merge environment, the PowerExchange Logger goes back to the oldest available RBA or timestamp. This process might be time-consuming depending on the number and size of available Logger archive logs.

The following messages are written to the PowerExchange message log to indicate that only zeroes are specified for the restart tokens:

PWX-06100 Sequence token 0000000000000000000000000000000000000000
PWX-06100 Logger   token 00000000000000000000000000000000

If the RESTART_TOKEN and SEQUENCE_TOKEN parameters are set to specific token values to define a specific restart point, PowerExchange Condense starts getting data from this restart point if it is a valid restart point in the Logger log files. The following messages in the PowerExchange message log identify the restart token values:

PWX-06100 Sequence token sequence_token_value 
PWX-06100 Logger   token restart_token_value

To determine the specific restart token values to use, you can use the DTLUAPPL or DTLUCDEP utility or review previous Condense job runs. In error recovery situations, Informatica Global Customer Support might provide these token values.

At this point in the initialization process, the Controller task starts the Command Handler and Condense subtasks of the Condense job.

PowerExchange Condense issues the following message to echo the restart tokens that are being used to define the start point for data extraction from the PowerExchange Logger:

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

After the restart point is established, PowerExchange Condense cleans up condense files and CDCT entries that have expired as a result of the cold start and writes checkpoint information to the current checkpoint file. Initialization is then complete as indicated by the following messages in the PowerExchange log:

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

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

Cold Start Processing

Cold Start Processing