Disabling progressive streaming with CLI/JDBC applications

Problem

Problem in cli driver with progressive streaming (Abstract) --------------------------------------------------------------------------------------- Problems may occur in DB2 zOS servers that support the progressive streaming interface when retrieving LOB or XML data if the application is setting rowset size > 1 once the cursor is opened and driver require more rows than what is present in the current client buffer. Consider the application has the following function flow SQL_ATTR_ROW_ARRAY_SIZE is set to 1 SQLExecute SQLFetch SQLFetch SQL_ATTR_ROW_ARRAY_SIZE is set to 6 Assume at this point of time, the current client driver buffer has only 2 rows remaining. Then for the next sqlfetch, driver has to go to server to get the remaining 4 rows. This will cause the server to close all the mode 3 references in the first client buffer. So accessing the first 2 rows of the rowset using mode 3 reference will throw error SQL30073N. Problem in jdbc driver with progressive streaming (Abstract) ---------------------------------------------------------------------------------------- In case of JDBC applications with pure locators, the locator remains valid until the transaction is committed. However, with progressive references the lob can become inaccessible sometime after moving to the next row in the Result Set. It may or may not happen - depends on the size of the lob, and the number of rows buffered in the driver before the next fetch goes to the server. The following error is thrown when the application tries to access the LOB reference that is already closed [jcc][10120][11936][3.63.80002] Invalid operation: Lob is closed. ERRORCODE=-4470, SQLSTATE=null java.io.IOException: [jcc][10120][11936][3.63.80002] Invalid operation: Lob is closed. ERRORCODE=-4470, SQLSTATE=null