JR33537: MWB DATA LINEAGE & DS COLUMN IMPACT ANALYSIS DONT FOLLOW RELATIO NSHIPS ACROSS A TRANSFORMER STAGE CONTAINING STAGE VARIABLES

APAR status

• Closed as fixed if next.

Error description

• When looking at column-level impact analysis, the existence of
  a stage variable in a transformer stage stops the relationship
  between output and input links being set correctly.
  
  For example, in the simplest form of Transformer stage,  if
  you have an input column dragged to the derivation of an output
  column, and do column-level impact analysis, you see the
  metadata flow going through the stage - the links both sides of
  the Transformer stage are highlighted. The output column is
  correctly shown as deriving from the input column.
  
  As soon as you add a stage variable to the Transformer stage,
  the flow stops at the stage itself, and only one link is
  highlighted. The relationship between the output and input
  columns has been lost, and the metadata does not flow through
  the stage - the output column appears not to derive from
  anywhere. This happens even if the stage variable is not
  related to the input or output column derivation in any way.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of DataStage column-level impact analysis
  or Metadata Workbench data lineage queries.
  ****************************************************************
  PROBLEM DESCRIPTION:
  If the DataStage job on which the lineage query is being
  performed contains a Transformer stage which has at least one
  Stage Variable defined, column derivations through that stage
  are not correctly reported. Input columns will not appear to
  flow to output columns. Data lineage appears to just "stop" at
  that Transformer.
  ****************************************************************
  RECOMMENDATION:
  Upgrade to version 8.5
  ****************************************************************
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• CLIENT
  

Fix information

Applicable component levels

• R810 PSN

     UP