Skip to main content

Software  >  Information Management  >  DB2 Product Family  >  

PQ88582: ODBC SUPPORT FOR 2MB SQL STATEMENT


 A fix is available

Obtain the fix for this APAR



APAR status
Closed as new function.

Error description
Currently, the maximum size in bytes of an SQL statement string
(including white spaces) allowed on the SQLPrepare,
SQLExecDirect and SQLNativeSql APIs is 32765.  DB2 V8 running in
NFM supports a maximum statement size of 2MB (2097152).
V8 DB2 ODBC will now support SQL statements up to 2MB in size
when connected to z/OS DB2 V8 servers running in NFM.
Local fix

Problem summary
****************************************************************
* USERS AFFECTED: All users of DB2 UDB for z/OS Version 8      *
*                 ODBC/CLI.                                    *
****************************************************************
* PROBLEM DESCRIPTION: 1. Currently, the maximum statement     *
*                         size that DB2 ODBC supports is       *
*                         32765 bytes, while DB2 V8 in New     *
*                         Function Mode accepts SQL            *
*                         statements up to 2MB.                *
*                      2. The ODBC DBRMs are coded in          *
*                         CCSID 1047.  However the DBRMs       *
*                         are precompiled with the default     *
*                         CCSID value which could be           *
*                         different from 1047.  SQLCODE        *
*                         -104 could occur as a result.        *
*                         Furthermore, a DBRM precompiled      *
*                         with NEWFUN(YES) can be bound only   *
*                         with DB2 z/OS V8 and later           *
*                         releases.  For the downward          *
*                         compatible ODBC driver, users        *
*                         need to be able to bind to DB2 for   *
*                         z/OS V7 and below.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
1. DB2 ODBC will support a maximum statement size of
   2097152 bytes (2MB) when connected to DB2 V8 for z/OS in
   New Function Mode,  during which time the new maximum SQL
   statement size will take effect for SQLPrepare(),
   SQLExecDirect(), SQLNativeSql() and SQLGetInfo()'s
   InfoType SQL_MAX_STATEMENT_LEN.

   If a SQL statement on a SQLPrepare() or SQLExecDirect()
   call has a length greater than 32765 bytes and the server
   that the application is connected to does not support a
   maximum statement size greater than 32KB, SQLPrepare() or
   SQLExecDirect will fail with SQLCODE -30005 and
   SQLSTATE 56072.

2. The CCSID precompiler option specifies the CCSID in which
   the source program is written.  Since all ODBC DBRMs are
   coded in CCSID 1047, they will be precompiled with the
   CCSID(1047) option.

   The NEWFUN precompiler option indicates whether to accept
   the syntax for DB2 Version 8 functions. A DBRM precompiled
   with NEWFUN(YES) can be bound only with Version 8 and later
   releases, even if the DBRM does not use any Version 8
   syntax.  ODBC users need to be able to find ODBC DBRMs to
   DB2 for z/OS Version 7 and below, therefore all ODBC DBRMs
   will be precompiled with NEWFUN(NO).  A DBRM precompiled
   with NEWFUN(NO) can be bound with any release of DB2 for
   z/OS, including DB2 Version 8.
Problem conclusion

Temporary fix

Comments

APAR information
APAR numberPQ88582
Reported component nameDB2 ODBC/JDBC/S
Reported component ID5740XYR02
Reported release817
StatusCLOSED UR1
PENoPE
HIPERNoHIPER
Special AttentionNoSpecatt
Submitted date2004-05-07
Closed date2004-07-30
Last modified date2004-10-05

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
CLICLIALLOCCLIDSTCLIEXECCLIMISCCLIQRY
CLIRETRCLISCNCLIUNICLIUTLDSN@LIASDSN@LICS
DSN@LIC1DSN@LIC2DSN@LIF4DSN@LIMSDSN@LINCDSN@LIQR
DSN@LIRRDSN@LIRSDSN@LIURDSN@LIVMDSN@LIV1DSN@LIV2
DSNAOCLIDSNAOC0ADSNAOC0EDSNAOC0FDSNAOC0GDSNAOC0H
DSNAOC0LDSNAOC0PDSNAOC0QDSNAOC0RDSNAOC0TDSNAOC0X
DSNAOC0YDSNAOC0ZDSNAOC01DSNAOC02DSNAOC07DSNAOC08
DSNAOC1VDSNAOC10DSNAOC11DSNAOC12DSNAOC17DSNAOC18
DSNAOSDKDSNSQL    

Publications Referenced

Fix information
Fixed component name DB2 ODBC/JDBC/S
Fixed component ID 5740XYR02

Applicable component levels
R817 PSY UQ91257   UP04/09/09 P F409

  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.

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Data Management
 Data Servers (Database Management Systems)
 DB2 for z/OS
 SQLJ/JDBC
 Software version:
  817
 Reference #:
  PQ88582
 IBM Group:
 Software Group
 Modified date:
 2004-10-05

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.