Notes about using the automatic reconnect facility

The automatic reconnect facility cannot be used if the UAP contains a LOCK statement that specifies UNTIL DISCONNECT.
If the UAP that uses a holdable cursor is being used, the automatic reconnect facility returns an error to the UAP, even if a transaction is not being processed.
If the JDBC driver¹ or DABroker for JAVA² accesses the system and a statement that applies over several transactions is effective, the JDBC statement becomes ineffective after the automatic reconnect facility reconnects the HiRDB client. In this case, the prepareStatement() method must be executed again.

¹ When the JDBC driver is used, a statement that applies over several transactions becomes effective when "CLOSE" or "RESERVE" is set to COMMIT_BEHAVIOR. COMMIT_BEHAVIOR can be set with the Properties info argument of the connect method in the Driver class, the Properties info argument of the DriverManager.getConnection method, or the COMMIT_BEHAVIOR key in a URL connection.

² When DABroker for JAVA is used, a statement that applies over several transactions becomes effective when the DABroker version is 03-06 or later and the DABroker for JAVA version is 02-10 or later.