JR30684: DATASTAGE JOBS THAT USE THE PLUG-IN MERGE STAGE RUN SUCCESSFULLY, BUT THEY FAIL AFTER BEING EDITED.

APAR status

• Closed as fixed if next.

Error description

• When the job that uses the Merge stage runs, these errors
  display:
  
  
  Every column name in column list must be preceded by either
  'File1' or 'File2'.
  Link property retrieval error.
  
  The issue is due to the following error:
  
  The output file of the Merge stage contains a list of
  comma-separated column names that come from the sequential input
  files. Each column name is preceded by the keyword File1 or
  File2. File1 specifies that the column belongs to the first
  sequential input file; File2 specifies the second sequential
  input file.
  For example, a column list might contain these entries:
  File1.Name, File2.Age, File2.Department.
  
  After the job is edited, the keywords File1 and File2 cannot be
  located in the output columns. Therefore an error message
  displays, and the job stops unexpectedly.
  

Local fix

• Complete these steps to edit the Merge stage:
  1. Click Output tab > Mapping tab.
  2. Drag the mapping for col1 and col2 from the navigation tree
  on the left.
  3. Click OK to close the window.
  4. Recompile the job and then run it.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Use of Merge stage
  ****************************************************************
  PROBLEM DESCRIPTION:
  The output file of the Merge stage contains a list of
  comma-separated column names that come from the sequential input
  files. Each column name is preceded by the keyword File1 or
  File2. File1 specifies that the column belongs to the first
  sequential input file; File2 specifies the second sequential
  input file.
  For example, a column list might contain these entries:
  
  File1.Name, File2.Age, File2.Department.
  
  
  After the job is edited, the keywords File1 and File2 cannot be
  located in the output columns. Therefore an error message
  displays, and the job stops unexpectedly.
  ****************************************************************
  RECOMMENDATION:
  See workaround in Local Fix field.
  Will be addressed in a future release.
  ****************************************************************
  

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