×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Our shop is in the process of upgrading our V5R4 OS to the V7R1.
When reviewing V6R1 memo to user, I see this:
New QueryCloseImplicit JDBC connection property
This release introduces performance improvements, including the new native
JDBC driver connection
property, QueryCloseImplicit. By default, this new property will be enabled.
Using this new QueryCloseImplicit property provides significant performance
improvement for many
applications that use native JDBC to query the System i database.
Although it is unlikely, with this new connection attribute, applications
might see slightly different
semantics in certain error scenarios. These error scenarios are APARable
situations with or without the
new function. With the new function, the error on the CLOSE call, which
should never happen except in
Chapter 2. i5/OS operating system 37
APARable situations, is reported on the ResultSet next() method call in
addition to the ResultSet close()
method to the JDBC application. Without the new function, the error is only
returned on the ResultSet
close() method.
Did anyone ever encounter any problem due to above enhancement? Also, does
anyone know what is "APARable situations" means?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
