This example uses the

UOW Count

and

Real-time Flush Latency in milli-seconds

attributes to control commit processing. The change data consists of UOWs of varying sizes. The commit control attributes have the following values:

Initially, PWXPC reads 900 complete UOWs in 5 seconds. At that point, the real-time flush latency interval has expired. As a result, PWXPC flushes the data buffer to commit change data to the targets. PWXPC then resets both the UOW counter and real-time flush latency timer. When PWXPC reaches the thousandth UOW, PWXPC does not commit change data to the targets because the UOW counter was reset to 0 after the last commit.

PWXPC reads the next 1,000 UOWs in 4 seconds, which is less than the real-time flush latency timer. PWXPC commits this change data to the target because the UOW counter has been met. PWXPC then resets the real-time flush latency timer and the UOW counter.

PWXPC continues to read change data and commit change data to the targets based on the UOW count or real-time flush latency limit, whichever is met first.

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