PI21922: ORDERBY GETS SQLCODE -199 ON DB2 PENDING DEFINITION CHANGES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• OrderBy gets SQLCODE -199 on DB2 pending definition changes
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 Z/OS.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: The following is fixed:                 *
  *                                                              *
  *                      1 - A SQLCODE= -199 / SQLCODEN199       *
  *                      is received when an ORDER BY clause     *
  *                      is defined for panel ADBPPDC 'DB2       *
  *                      Pending Definition Changes':            *
  *                                                              *
  *                      DSNT408I SQLCODE = -199, ERROR:         *
  *                      ILLEGAL USE OF KEYWORD ORDER.           *
  *                      TOKEN                                   *
  *                      >ERR_STMT< >WNG_STMT< GET               *
  *                      SQL SAVEPOINT HOLD FREE                 *
  *                      ASSOCIATE WAS  EXPECTED                 *
  *                      DSNT418I SQLSTATE   = 42601             *
  *                      SQLSTATE RETURN CODE                    *
  *                                                              *
  *                      2 - When a user issues the 'ALT -       *
  *                      Alter or Rename a database' line        *
  *                      command on panel ADB21D 'Databases'     *
  *                      to alter a database, and uses           *
  *                      Change Management (CM), any             *
  *                      pending changes are shown on            *
  *                      panel ADB2CCR 'Pending changes',        *
  *                      with user options of APPLY or           *
  *                      SUPERSEDE. Upon selection of            *
  *                      the SUPERSEDE option and analyzing      *
  *                      the registered change, the new          *
  *                      changes are not populated correctly,    *
  *                      resulting in Merge failure              *
  *                      ADBC002E / msgadbc002e:                 *
  *                                                              *
  *                      ADBC002E - Severe error. Merge          *
  *                      terminates                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The following are fixed:
  
  1 - A SQLCODE=-199 / SQLCODEN199 is received when an ORDER BY
  clause is defined for panel ADBPPDC, and an incorrect SQL
  statement is generated.
  
  2 - When using the SUPERSEDE option while altering a database
  via Change Management, the changes are not populated correctly,
  resulting in a Merge failure.
  

Problem conclusion

• Problems have been resolved.
  

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:

  UI20548 UI20549

Modules/Macros

•    ADBMAIN  ADB21DA0 ADB27CX
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RA20 PSY UI20548

     UP14/08/20 P F408

• RB10 PSY UI20549

     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.