JR57919: Column lineage is broken when Shared Containers are used

APAR status

• Closed as program error.

Error description

• User defines a job design using shared containers.
  The columns used before shared container can be ignored inside
  shared container. Therefore the flow of the data looks like
  interrupted.
  However this design is acceptable inside DataStage as long as
  the columns with the same names are used on the output of the
  Shared Container. Such situation lead to broken column lineage.
  The fix addresses such situation to check the input and output
  columns to have full column lineage.
  

Local fix

Problem summary

• *********************************************
  APAR Users Affected:
  *********************************************
  Users running column lineage on the job that contains shared
  containers
  
  *********************************************
  APAR Problem Description:
  *********************************************
  User defines a job design using shared containers. The columns
  used before shared container can be ignored inside shared
  container. Therefore the flow of the data looks like
  interrupted. However this design is acceptable inside DataStage
  as long as the columns with the same names are used on the
  output of the Shared Container. Such situation lead to broken
  column lineage. The fix addresses such situation to check the
  input and output columns to have full column lineage.
  
  *********************************************
  APAR Recommendation:
  *********************************************
  Apply the fix for JR57919
  
  *********************************************
  

Problem conclusion

• Apply the fix for JR57919
  

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:

Fix information

• Fixed component name

  IS GOVCATLOG

• Fixed component ID

  5724Q36GC

Applicable component levels

• RB50 PSY

     UP