JR27358: ENABLE CLI KEYWORD SETTING PATCH1=1 IN DB2 UDB VERSION 9

DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as new function.

Error description

• The CLI keyword setting PATCH1=1 is used in DB2 UDB Version 7 to
  replace COUNT(expression) with COUNT(*) in SQL queries.  This
  setting has not been available in DB2 UDB Version 8 and Version
  9.
  
  The setting is a workaround for applications that use
  COUNT(expression) in SQL queries with DB2 servers that do not
  support this syntax.
  
  For example, a query generated by Microsoft Access might contain
  the following syntax:
  
  SELECT COL1, COUNT(1) FROM TAB1 WHERE ...
  
  DB2 Version 7 on z/OS does not support the COUNT(1) syntax, thus
  returns error SQL0111N (column function does not include a
  column name).
  
  With PATCH1=1 set in the db2cli.ini file on the Version 7
  client, the query is changed to:
  
  SELECT COL1, COUNT(*) FROM TAB1 WHERE ...
  
  This syntax is accepted by DB2 z/OS Version 7 and no error
  occurs.
  
  The PATCH1=1 setting has not been available in DB2 UDB Version
  8. This APAR will track the fact that support for this CLI
  keyword setting is being added to DB2 UDB version 8 and version
  9.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  PATCH1=1 is not enabled to replace COUNT(expression) with
  COUNT(*) for sql queries
  ****************************************************************
  PROBLEM DESCRIPTION:
  The CLI keyword setting PATCH1=1 is used in DB2 UDB Version 7
  toreplace COUNT(expression) with COUNT(*) in SQL queries.  This
   setting has not been available in DB2 UDB Version
  9.
       The setting is a
  workaround for applications that use        COUNT(expression)
  in SQL queries with DB2 servers that do not   support this
  syntax.
        For example, a query generated by
  Microsoft Access might       contain
          the following syntax:
  
      SELECT COL1, COUNT(1) FROM TAB1 WHERE ...
            DB2 Version 7 on
  z/OS does not support the COUNT(1) syntax, thus
              returns error
  SQL0111N (column function does not include a   column name).
  
      With PATCH1=1 set in the db2cli.ini
  file on the Version 7     client, the query is changed to:
  
      SELECT COL1, COUNT(*) FROM TAB1 WHERE ...
            This syntax is
  accepted by DB2 z/OS Version 7 and no error  occurs.
  
     The PATCH1=1 setting has not been
  available in DB2 UDB Version  9. This APAR will track the fact
  that support for this CLI      keyword setting is being added to
  DB2 UDB version        9.
  ****************************************************************
  RECOMMENDATION:
  Upgrade to db2 v91fp8 or later.
  ****************************************************************
  

Problem conclusion

• Fixed in db2 v91fp8.
  

Temporary fix

Comments

APAR Information

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

  JR24008

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

Fix information

• Fixed component name

  DB2 CEE WINDOWS

• Fixed component ID

  5765F3001

Applicable component levels

• R910 PSN

     UP