This example uses the

Maximum Rows Per commit

and

UOW Count

attributes to control target commit processing. The change data consists of UOWs of the same size. Each UOW contains 1,000 change records. The commit control attributes have the following values:

Based on the maximum rows value, PWXPC flushes the data buffer after reading the first 300 records in a UOW. This action commits the change data to the targets. PWXPC continues to commit change data to the targets every 300 records.

PWXPC commits change data on UOW boundaries only for the UOW count and real-time flush latency interval. If the real-time flush latency interval expires before PWXPC reads 300 change records, PWXPC still commits change data based on the maximum rows value because that threshold is met before a UOW boundary occurs.

When the end of the UOW is read, PWXPC commits the change data because the

UOW Count

value is 1. PWXPC resets the UOW and maximum rows counters and the real-time flush latency timer each time PWXPC issues a commit. Because all of the UOWs have the same number of change records, PWXPC continues to read change data and commit change data to the targets at the same points in each UOW.

In this example, PWXPC commits change data at the following points: