JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

The following conditions apply:
• if maxPoolSize >= 0 and minPoolSize = 0, then maxIdleTime is not applied.
• If maxPoolSize > 0 and minPoolSize > 0,
and maxIdleTime > 0, a connection when closed is added to the free pool. After the
number of seconds specified using the maxIdleTime property, the number of connections
in the pool is equal to minPoolSize, and any extra connection is hard closed.
◦
◦ and maxIdleTime = 0 (default), then connections are sent to the free pool immediately
until the free pool size is equal to minPoolSize, and any connection closed subsequently
is hard closed.
• Data type — int
• Units — seconds
• Default — 0 (No timeout.)
• Range — 0 to 2147483647
• Any negative value is treated as 0.
To assign 300 to the maxIdletime property, enter the following:
-Djdbcmx.maxIdleTime=300
language Property
The language property sets the language to be used in error messages. For more information on
this property, see “Internationalization” (page 68).
• Data type — String
• Default — None
• Value — Any valid Java Canonical Name as described in the Canonical Name for java.io
and java.lang API column of the Oracle documentation: http://download.oracle.com/
javase/1.5.0/docs/guide/intl/encoding.doc.html
To set the language to shift-JIS, enter the following:
Japanese: language=SJIS
transactionMode Property
The transactionMode property provides control over how and when transactions are performed.
Specify the transactionMode property as:
String
The default is mixed. The allowed values are:
internal
Specifies that transactions are always performed within a JDBC/MX driver-managed
transaction. If an external transaction exists when internal transaction mode is in
effect, the external transaction is suspended and the SQL statement is executed
within a JDBC/MX driver-managed transaction. Upon completion of the driver’s
internally managed transaction, the existing external transaction is resumed. The
Connection autocommit flag maintains a value of true when in internal transaction
mode.
NOTE: Using internal transactionMode for select statements performed in external transactions
causes JDBC/MX to throw an "invalid transaction state" exception. Therefore, do not specify
internal transactionMode under these conditions.
JDBC/MX Properties 29