Table of Contents

Search

  1. Preface
  2. PowerExchange Navigator Introduction
  3. Data Maps
  4. Data Maps for Specific Data Sources
  5. Copybooks
  6. Registration Groups and Capture Registrations
  7. Extraction Groups and Extraction Maps
  8. Personal Metadata
  9. Database Row Test
  10. PowerExchange Navigator Examples
  11. Appendix A: PowerExchange Functions for User-Defined Fields
  12. Appendix B: User Access Method Programs
  13. Appendix C: Application Groups and Applications
  14. Appendix D: Data Map Properties
  15. Appendix E: Record, Field, and Table Properties
  16. Appendix F: DTL__CAPXTIMESTAMP Time Stamps
  17. Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook

Navigator User Guide

Navigator User Guide

Condense Options

Condense Options

The
Condense
option in a capture registration controls whether you can use PowerExchange Condense or PowerExchange Logger for Linux, UNIX, and Windows processing for the registered source. For PowerExchange Condense on i5/OS or z/OS, the option also indicates the type of condense processing.
From the PowerExchange Navigator, you can edit the
Condense
option for an existing capture registration without versioning the registration. For example, you can switch from None to Part or Full to Part.
The Condense options are:
None
The capture registration is not eligible for use by PowerExchange Condense or the PowerExchange Logger for Linux, UNIX, and Windows.
Part
The capture registration is eligible for use by PowerExchange Condense or the PowerExchange Logger for Linux, UNIX, and Windows. PowerExchange Condense uses the registration for partial condense processing.
With this option, only the changes in UOWs that complete successfully on the source are written to PowerExchange Condense condense files or PowerExchange Logger log files. PowerExchange writes all changes for columns of CDC interest, not just the latest changes, in chronological order based on UOW end time. This option maintains transactional consistency.
Informatica recommends that you select the
Part
option even if you do not plan to use PowerExchange Condense or the PowerExchange Logger. You can implement PowerExchange Condense or the PowerExchange Logger later without having to update the registration.
Full
The capture registration is eligible for use by PowerExchange Condense on i5/OS or z/OS for full condense processing.
PowerExchange Condense accumulates changes in keyed condense files by having later changes replace earlier changes. This option does not maintain transactional consistency.
The following restrictions apply to full condense processing:
  • For Adabas and IDMS log-based CDC sources, full condense processing is not available.
  • For PowerExchange Condense on i5/OS, full condense processing is available only for tables that have primary keys and DDS files that are defined with a unique key.
  • For PowerExchange Condense on z/OS, full condense processing is available for tables or data maps that specify key columns.
Use this option only if the source has a unique key. PowerExchange Condense uses the unique key as part of the key in the condense file to maintain a single before and after image.
To be allowed to update a unique key while using full condense processing, you must specify KEY_CHANGE_ALW=Y in the PowerExchange Condense configuration file. With this setting, PowerExchange Condense ignores the key update and continues full condense processing.

0 COMMENTS

We’d like to hear from you!