JR58041: PROBLEM WITH PARSING CONNECTOR STAGE WITH SQL STATEMENT FROM EXTERNAL FILE

APAR status

• Closed as program error.

Error description

• The lineage reports show only the design time relationships and
  not the relationships that were derived at run time.
  The datastage job uses parameters to define the source and
  targets and the job has a set of default parameters.  It is
  only with these values that sources and targets appear in the
  lineage reports. When the operational meta data is added to the
  repository, it is expected that the new sources and targets
  would be shown in the lineage reports. However this is not the
  case.  The lineage reports are not affected with the
  operational data.
  

Local fix

• Best practices doc says that user shouldn't use path to SQL
  files, better is to provide sql statement:
  https://www.ibm.com/support/knowledgecenter/en/SSZJPZ_11.3.0/com
  .ibm.swg.im.iis.mdwb.doc/topics/c_optimize_ds_job_for_lineage.ht
  ml
  

Problem summary

• *********************************************
  APAR Users Affected:
  *********************************************
  Users developing jobs containing connector stages having path to
  the SQL file instead of SQL statement itself
  
  *********************************************
  APAR Problem Description:
  *********************************************
  IGC code handing connector stages expeced SQL statements
  therefore when one pass path to the fail, parsing failed.
  
  *********************************************
  APAR Recommendation:
  *********************************************
  Apply the fix for JR58041
  
  *********************************************
  

Problem conclusion

• Apply the fix for JR58041
  

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