PI21935: IMPORT FROM DDL INTO CM OF A LONG 'CREATE TABLE' STATEMENT (>3000 CHARACTERS) STATEMENT IS BROKEN AT 3000TH CHARACTER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• There are multiple issues in this scenario. An IMPORT of a
  long 'CREATE TABLE' statement (>3000 characters) from a DDL
  file, statement is broken at 3000th character and trailing
  truncated statement is treated as part of a new statement.
  
  Since IMPORTed statement itself is not complete & accurate,
  EXPORT of the change containing these statements fails with
  parser error. Another issue is that, even after parser error
  in EXPORT, we show a successful completion message "Export
  changes successful. The total number of exported changes
  are xx.".
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Administration Tool for z/OS    *
  *                 who use the Change Management (CM) Export    *
  *                 Change function.                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: The DB2 Administration Tool for z/OS'   *
  *                      CM Export Change function will          *
  *                      truncate a long change statement into   *
  *                      several fragments and export them       *
  *                      into the output data set incorrectly.   *
  *                      Additionally, if specifying Mask        *
  *                      the CM Export Change Batch job          *
  *                      returns Return Code 0 / RC = 0 but      *
  *                      the job log shows a parser error        *
  *                      because the long change statement       *
  *                      has been truncated into several         *
  *                      fragments which will be input to        *
  *                      the Parser:                             *
  *                                                              *
  *                      Unexpected token after >xx< keyword     *
  *                      - expected >yy< keyword                 *
  *                                                              *
  *                      ADB2PA: The following statement         *
  *                              could not be parsed :           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The CM Export Change function will truncate a long change
  statement into several fragments and export them into the
  output data set incorrectly.  Additionally, if specifying Mask,
  the CM Export Change Batch job returns Return Code 0 / RC = 0
  but the job log shows a parser error because the long change
  statement has been truncated into several fragments which will
  be input to the Parser.
  

Problem conclusion

• CM Export Change function has been modified to resolve
  the truncation problem for the long change statements.
  CM Export Change function has been modified to set a
  return code > 0 when encountering a parser error.
  

Temporary fix

Comments

• ×**** PE14/10/29 FIX IN ERROR. SEE APAR PI23916  FOR DESCRIPTION
  

APAR Information

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

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

Modules/Macros

•    ADB2ISQ
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RB10 PSY UI20545

     UP14/08/20 P F408

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.