A fix is available
APAR status
Closed as new function.
Error description
Currently, ODBC provides an array input method for performing bulk inserts. This method involves the binding of parameter markers to arrays of application variables using the SQLBindParameter() call. The application only needs to call SQLExecute() once and the driver sends the inserts one by one to the database. This APAR will optimize DB2 ODBC's bulk insert to use the multi-row INSERT statement when connected to DB2 for z/OS.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of DB2 UDB for z/OS Version 8 * * ODBC/CLI. * **************************************************************** * PROBLEM DESCRIPTION: Currently for bulk inserts, DB2 ODBC * * still inserts one row at a time * * instead of issuing a multi-row INSERT * * statement. * **************************************************************** * RECOMMENDATION: * **************************************************************** DB2 ODBC already provides an array input method for applications performing bulk inserts. This method involves the binding of parameter markers to arrays of application variables using the SQLBindParameter() call. This saves the application from having to call SQLExecute() repeatedly on the same INSERT statement. However, once the driver receives the arrays of input data, it still sends the inserts to the database one row at a time. This APAR will optimize DB2 ODBC's array input method for bulk inserts to use the multi-row INSERT statement instead of performing INSERTs for each row.
Problem conclusion
Temporary fix
Comments
The multi-row INSERT statement is only available in DB2 for z/OS V8 running in New Function Mode. ODBC will only perform multi-row INSERT when it determines that the local DB2 server and the target data source are DB2 z/OS V8 servers running in New Function Mode. In all other cases, the driver will continue to send one INSERT at a time for bulk inserts.
APAR Information
APAR number
PQ92072
Reported component name
DB2 ODBC/JDBC/S
Reported component ID
5740XYR02
Reported release
817
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2004-07-27
Closed date
2005-08-31
Last modified date
2005-10-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK06883
Modules/Macros
CLI CLIALLOC CLICSR CLICTX CLICVT CLIDST CLIERR CLIEXEC CLIEXP CLIICONV CLIINI CLILAT CLILOB CLIMDT CLIMEM CLIMISC CLIMVSF1 CLIMVSF2 CLIMVSF3 CLIMVSF5 CLIOPT CLIPET CLIQRY CLIRETR CLISCHEM CLISCN CLISDA CLISMP CLISQL CLISQLNF CLISYS CLITRS CLIUNI CLIUTL CLIVAL CLI400 DSN@LIAS DSN@LICS DSN@LIC1 DSN@LIC2 DSN@LIF4 DSN@LIMS DSN@LINC DSN@LINF DSN@LIQR DSN@LIRR DSN@LIRS DSN@LIUR DSN@LIVM DSN@LIV1 DSN@LIV2 DSNAOCLI DSNAOCPG DSNAOC0A DSNAOC0B DSNAOC0C DSNAOC0D DSNAOC0E DSNAOC0F DSNAOC0G DSNAOC0H DSNAOC0I DSNAOC0J DSNAOC0K DSNAOC0L DSNAOC0M DSNAOC0O DSNAOC0P DSNAOC0Q DSNAOC0R DSNAOC0S DSNAOC0T DSNAOC0U DSNAOC0V DSNAOC0W DSNAOC0X DSNAOC0Y DSNAOC0Z DSNAOC00 DSNAOC01 DSNAOC02 DSNAOC03 DSNAOC04 DSNAOC05 DSNAOC06 DSNAOC07 DSNAOC08 DSNAOC09 DSNAOC1L DSNAOC1Q DSNAOC1R DSNAOC1S DSNAOC1T DSNAOC1U DSNAOC1V DSNAOC1W DSNAOC10 DSNAOC11 DSNAOC12 DSNAOC13 DSNAOC14 DSNAOC15 DSNAOC16 DSNAOC17 DSNAOC18 DSNAOC19 DSNAOC21 DSNAOC22 DSNAOSDK DSNAOTRC DSNTIJCL JDB8817J SQLTCLI SQLTCLQ
Fix information
Fixed component name
DB2 ODBC/JDBC/S
Fixed component ID
5740XYR02
Applicable component levels
R817 PSY UK06883
UP05/09/23 P F509
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.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"817"}]
Document Information
Modified date:
04 March 2021