Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data
  26. POWERCENTERHELP

Advanced Workflow Guide

Advanced Workflow Guide

Transformation Scope

Transformation Scope

You can configure how the Integration Service applies the transformation logic to incoming data with the Transformation Scope transformation property. When the Integration Service processes a transformation, it either drops transaction boundaries or preserves transaction boundaries, depending on the transformation scope and the mapping configuration.
You can choose one of the following values for the transformation scope:
  • Row.
    Applies the transformation logic to one row of data at a time. Choose Row when a row of data does not depend on any other row. When you choose Row for a transformation connected to multiple upstream transaction control points, the Integration Service drops transaction boundaries and outputs all rows from the transformation as an open transaction. When you choose Row for a transformation connected to a single upstream transaction control point, the Integration Service preserves transaction boundaries.
  • Transaction.
    Applies the transformation logic to all rows in a transaction. Choose Transaction when a row of data depends on all rows in the same transaction, but does not depend on rows in other transactions. When you choose Transaction, the Integration Service preserves incoming transaction boundaries. It resets any cache, such as an aggregator or lookup cache, when it receives a new transaction.
    When you choose Transaction for a multiple input group transformation, you must connect all input groups to the same upstream transaction control point.
  • All Input.
    Applies the transformation logic on all incoming data. When you choose All Input, the Integration Service drops incoming transaction boundaries and outputs all rows from the transformation as an open transaction. Choose All Input when a row of data depends on all rows in the source.
The following table lists the transformation scope values available for each transformation:
Transformation
Row
Transaction
All Input
Aggregator
-
Optional.
Default.
Transaction control point.
Application Source Qualifier
n/a
Transaction control point.
-
-
Custom
Optional.
Transaction control point when configured to generate commits or when connected to multiple upstream transaction control points.
Optional.
Transaction control point when configured to generate commits.
Default.
Always a transaction control point.
Generates commits when it has one output group or when configured to generate commits. Otherwise, it generates an open transaction.
Data Masking
Default. Read only.
-
-
Expression
Default. Does not display.
-
-
External Procedure
Default. Does not display.
-
-
Filter
Default. Does not display.
-
-
HTTP
Default. Read only.
-
-
Java
Default for passive transformations.
Optional for active transformations.
Default for active transformations.
Joiner
-
Optional.
Default.
Transaction control point.
Lookup
Default. Does not display.
-
-
MQ Source Qualifier
n/a
Transaction control point.
-
-
Normalizer (VSAM)
n/a
Transaction control point.
-
-
Normalizer (relational)
Default. Does not display.
-
-
Rank
-
Optional.
Default.
Transaction control point.
Router
Default. Does not display.
-
-
Sorter
-
Optional.
Default.
Transaction control point.
Sequence Generator
Default. Does not display.
-
-
Source Qualifier
n/a
Transaction control point.
-
-
SQL
Default for script or query mode SQL transformations.
Optional.
Transaction control point when configured to generate commits.
Optional.
Stored Procedure
Default. Does not display.
-
-
Transaction Control
Default. Does not display.
Transaction control point.
-
-
Union
Default. Does not display.
-
-
Unstructured Data
Default. Read only.
-
-
Update Strategy
Default. Does not display.
-
-
XML Generator
-
Optional.
Transaction when the flush on commit is set to create a new document.
Default. Does not display.
XML Parser
Default. Does not display.
-
-
XML Source Qualifier
n/a
Transaction control point.
-
-


Updated July 04, 2018