PK34723: KEYWORD NO INCORRECTLY CONSIDERED A RESERVE WORD

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Using BMC-PLUS syntax specifying the keyword NO gets messages
  INZU010I
  INZU016E INTO STATEMENT SYNTAX IS INVALID
  INZU039E FATAL SYNTAX ERROR
  Keyword NO is incorrectly processed as a reserved word.
  ( PB 6562 )
  ADDITIONAL SYMPTOMS:
  1. Running BMG-PLUS syntax specifying SELECT with UNION ALL gets
     INZU063I UNSUPPORTED SELECT
     DSNT408I SQLCODE = -104
     DSNT418I SQLSTATE   = 42601 SQLSTATE RETURN CODE
     ( PB 8561 )
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 High Performance Unload.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Using BMC-PLUS syntax specifying the    *
  *                      keyword NO gets messages INZU010I       *
  *                      INZU016E INTO STATEMENT SYNTAX IS       *
  *                       INVALID                                *
  *                      INZU039E FATAL SYNTAX ERROR             *
  *                      Keyword NO is incorrectly processed as  *
  *                      a reserved word. ( PB 6562 )            *
  *                      ADDITIONAL SYMPTOMS:                    *
  *                      1. Running BMG-PLUS syntax specifying   *
  *                       SELECT with UNION ALL gets             *
  *                         INZU063I UNSUPPORTED SELECT          *
  *                         DSNT408I SQLCODE = -104              *
  *                         DSNT418I SQLSTATE   = 42601          *
  *                       SQLSTATE RETURN CODE  ( PB 8561 )      *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Module inzpyacc was changed to use a subcontext when analyzing
  the INTO clause. For the first column of the list, the only non
  supported column names are now NAME, RECORDID and FROM. For the
  other columns of the list, the only non supprted column name is
  FROM. These non supported column names should be specified
  between quotes to be accepted.
  The same problem could also occur for the following clauses of
  the unload plus syntax:
      *  CNTLDDN
      * INFILE
      * DDLDDN
      * EXIT
      * SORTDEVT
      * UNLOADDDN
      * UNLOADEXIT
      * SHRLEVEL CHANGE CONSISTENT YES XBMID
  The analysis of these clauses has also been fixed.
  
  1. Module inzpyacc was changed for the Unload plus syntax
  processing to recognize the UNION and ALL keywords, and the
  grammar rules were changed for the fullselect analysis.
  New module inz0yacc was created for analysis of SELECT, WHERE
  and ORDER clauses.
  

Problem conclusion

• APPLY the PTF.
  

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:

  UK20039 UK20040

Modules/Macros

•    INZUTILB
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R210 PSY UK20039

     UP06/12/16 P F612

• R220 PSY UK20040

     UP06/12/16 P F612

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.