Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why my stored procedure with OUT parameter works in JDBC-ODBC Bridge and IDS Server 3.2.x but not in IDS Server 3.5.x?

April 26, 2017bridge IDs jdbc-odbc parameter procedure server stored

0

Posted

Why my stored procedure with OUT parameter works in JDBC-ODBC Bridge and IDS Server 3.2.x but not in IDS Server 3.5.x?

1 Answer

0

Posted

Both JDBC-ODBC Bridge and IDS Server 3.2.x uses ODBC 2.x API, which makes OUT parameter values available once the stored procedure is executed. The problem for this behavior is that some stored procedures contain multiple SQL statements, and the OUT parameter value may not be assigned until all statements are processed. IDS Server 3.5.x uses ODBC 3.5 API, which changes how OUT parameters values are assigned to address this problem. Refer to topic J13 for details.