PM37571: BIND QUERY FAILED WITH INCORRECT PARSING OPTIONS IN DECP

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• BIND QUERY failed when parsing options in DSNHDECP are
  incorrect.
  
  The DSNT281I message shown in the bind output is like:
  
  DSNT281I  .ZT98 BIND QUERY FOR QUERYNO = 88888888 NOT
              SUCCESSFUL,
              REASON:  STATEMENT TEXT ERROR
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS users using the          *
  *                 BIND QUERY command to utilize                *
  *                 the instance-level hint support.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Sometimes BIND QUERY job may fail       *
  *                      and return a DSNT281I message with      *
  *                      the reason text STATEMENT SYNTAX        *
  *                      ERROR when processing a static          *
  *                      query or a dynamic one prepared         *
  *                      with DYNAMICRULES(BIND).                *
  ****************************************************************
  * RECOMMENDATION: N/A.                                         *
  ****************************************************************
  During the BIND QUERY processing, DB2 will process the
  statement text provided in the DSN_USERQUERY_TABLE.
  Certain parsing options are needed in order to process
  the statement text correctly. If the parsing options
  are incorrect, BIND QUERY may fail and DSNT281I message
  can be issued with the reason text STATEMENT SYNTAX ERROR.
  
  The problem is that before the fix,  DB2 will only use the
  parsing options in the DECP. However, for certain types of
  queries, such as static queries, their packages are bound
  with some parsing options that are different from the DECP
  values. It can cause DB2 to issue DSNT281I error message
  with reason text STATEMENT TEXT ERROR.
  
  In order to make the BIND QUERY successful, the user is
  recommended to do the following.
  
  (1) For static queries and dynamic queries prepared with
  DYNAMICRULES(BIND), the user is recommended to populate the
  PACKAGE / COLLECTION / VERSION information about which package
  the query is from in the DSN_USERQUERY_TABLE.
  
  (2) For dynamic queries, the user needs to use upper case for
  SQL keywords and DB2 object names.
  
  With above information provided and with the APAR applied,
  DB2 will retrieve the correct parsing options. Thus the error
  described above can be solved.
  
  Additional Keywords:
  MSGDSNT281I SQLBINDQUERY
  

Problem conclusion

Temporary fix

Comments

• The BIND QUERY error described above is improved
  by utilizing the PACKAGE / COLLECTION / VERSION
  information provided by the user in the
  DSN_USERQUERY_TABLE to retrieve the correct
  parsing options.
  

APAR Information

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

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

  UK70832

Modules/Macros

• DSNHAPL2 DSNHSM1  DSNHSM2V DSNHXLTR DSNXEVPH
  DSNXHNTB DSNXOBNQ
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK70832

     UP11/09/04 P F109

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.