Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace App Connect
Created by Guest
Created on Jul 27, 2017

IIB - passing more than one row (e.g. using a multi-dimensional array) to the database using the PASSTHRU function

Currently, when we want to INSERT several rows on a table using parameter markers in a single (batch) operation with IIB PASSTHRU function:
[PASSTHRU function]

we have to use the following syntax (in this example, to insert 5 rows):

INSERT INTO [schema].[table] (C1,C2,C3,C4) VALUES (?,?,?,?),(?,?,?,?),(?,?,?,?),(?,?,?,?),(?,?,?,?)

Although this works, we think that the best way to insert multiple rows at a time when using parameter markers should be to use this syntax (irrespective of the number of rows to insert):

INSERT INTO [schema].[table] (C1,C2,C3,C4) VALUES (?,?,?,?)

and then provide the exact values to be used for the multiple rows to be inserted using a bidimensional array (one dimension for each row and the other one for the column values) or similar structure.
Using this SQL syntax will reduce the number of different statements that need to be prepared and stored in the database and the integration node irrespective of how many rows you want to insert in a single execution.

This can be seen in the following article (by one of the best IBM Db2 experts) in the case of Db2 (see the section: "Insert multiple rows at a time"):
[Tips for getting the best INSERT performance]

If you're like most people and use JDBC or ODBC, then it's a little different. The SQL only specifies one row, but you use ODBC / JDBC constructs to tell the driver how many rows' worth of data you want to push down in a single execution.

/* Multiple rows at a time in ODBC */
PreparedStatement SQLCHAR *stmt = (SQLCHAR *) "INSERT INTO t(c1, c2) VALUES(?, ?)";
SQLSMALLINT parameter1[] = { 121, 131, 141 };
char parameter2[][20] = { "Toronto", "Vancouver", "Ottawa" };
int row_array_size = 3;
cliRC = SQLPrepare(hstmt, stmt, SQL_NTS);
cliRC = SQLSetStmtAttr(hstmt, SQL_ATTR_PARAMSET_SIZE, (SQLPOINTER) row_array_size, 0);
cliRC = SQLBindParameter(hstmt, 1, SQL_PARAM_INPUT, SQL_C_SHORT, SQL_SMALLINT, 0, 0, parameter1, 0, NULL);
cliRC = SQLBindParameter(hstmt, 2, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_VARCHAR, 20, 0, parameter2, 20, NULL);
cliRC = SQLExecute(hstmt);

/* Multiple rows at a time in JDBC */
PreparedStatement prepStmt = con.prepareStatement( "INSERT INTO t VALUES (?,?)");
for ... object : objects ... {
prepStmt.setInt (1,object.parameter1());
prepStmt.addBatch ();
int [] numUpdates=prepStmt.executeBatch(); /* Generally you would do this periodically in the loop too */

However, this is not possible when using IIB PASSTHRU function, as it was explained by L3 on the associated PMR.
Note: we've seen this limitation when dealing with SQL Server, but we think the same applies to other database managers.

Idea priority Medium
RFE ID 108337
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Oct 8, 2020

    RFE Review. Thank you for raising this RFE and apologies for the time period it has been in Submitted Status. This is an interesting suggestion, and one which you've clearly thought a lot about. At times, ESQL array handling whilst possible with the assistance of ROW variables or the logical tree, it can be a little awkward which might make implementation of the suggestion tricky. We are interested in continuing to monitor this suggestion for popularity (noting that it doesn't seem to have attracted votes so far despite being open for several years) so are updating the status to Uncommitted Candidate.