JR38482: 1. SUPPORT FOR "CURRENT DATE" WHEN PARSING CUSTOM SQL STATEMENTS

APAR status

• Closed as program error.

Error description

• 1. ANSI SQL parser is not accepting the DB2-specific double
  token "current date".  Thus the DS Stage is not properly linked
  to the Database Table.
  
  2.  When Custom SQL cannot be parsed, the MWB attempts to link
  the Stage to a Database Table using other Stage Variables, in
  this case the Database Name, User Nmae (default for Schema) and
  Table Name.  The Table Name is not provided in the case of
  defining Custom SQL Statements.  The MWB incorrectly linked the
  DS Stage to a Table which appeared within the Database and
  Schema read from the DS Stage variables.
  
  To be addressed by:
  
  1.  Support for "current date" when parsing Custom SQL
  Statements
  
  2.  Ignore DS Stage to Database Table linking when the Table
  Name variable is not defined
  

Local fix

Problem summary

• Automated services cannot parse DB2 token "current date"
  

Problem conclusion

• Fix has been made to Automated Services which now parses DB2
  token "current date".
  

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

  METADATA WORKBE

• Fixed component ID

  5724S4100

Applicable component levels

• R812 PSY

     UP