When you create a capture registration for a data source, you must set the

Condense

option to

Full

or

Part

to indicate the type of condense processing.

If you select

Full

, PowerExchange Condense uses full condense processing. Full condense processing does not maintain transactional integrity, but it can decrease the amount of change records that are processed and extracted. During a full condense cycle, PowerExchange Condense records only the last change made to a row in a condense file. If multiple changes are made to the same row, later changes supersede earlier changes, leaving only the latest change. Use the following criteria to determine if you want to use full condense processing:

If you select the

Part

option, PowerExchange Condense uses partial condense processing. Partial condense processing maintains transactional integrity because PowerExchange Condense does not eliminate any change. During a partial condense cycle, PowerExchange Condense writes all of the changes for successfully completed UOWs to condense files, in chronological order by UOW end time. If a DB2 for i5/OS table is updated outside of commit control, PowerExchange Condense writes changes in the order that each update occurred. To save disk space, PowerExchange Condense organizes records in partial condense files into 32 KB blocks. The records might appear incorrect if you access them through the

i5/OS

DSPPFM command.