JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.1 (H06.23+, J06.12+)

minPoolSize int
Property.
can be in the free
connection pool. See
minPoolSize Property.
maxPoolSize int
See maxPoolSize
Property.
Sets maximum number of
physical connections that
the pool should contain.
This number includes both
free connections and
connections in use. See
maxPoolSize Property.
blobTableName String
See LOB Table
Name Properties.
Specifies the LOB table for
using BLOB columns.
clobTableName String
See LOB Table
Name Properties.
Specifies the LOB table for
using CLOB columns.
transactionMode String
See transactionMode
Property.
Sets the transaction mode,
which provides control over
how and when transactions
are performed. See
transactionMode Property.
Note: Do not add the jdbcmx. prefix to the property name when the properties are
given as a parameter to the connection method or when using the data source.
The prefix is not needed to identify the property type because the property is being
passed to a JDBC/MX driver object. Use the jdbcmx. prefix only in the command
line as described under
Setting Properties in the Command Line.
Guidelines for Using Connections with the DriverManager Class
Java applications can specify the properties in the following ways:
Using JDBC/MX properties with the -D option in the command line. If used, this option applies to
all JDBC connections using the
DriverManager within the Java application. The format is to enter
the following in the command line:
-Djdbcmx.property_name=property_value
For example in a command line, -Djdbcmx.maxStatements=1024
Using the java.util.properties parameter in the getConnection method of DriverManager.
The properties passed through the java.util.properties parameter have a higher precedence over
the command-line properties.
The connection pooling feature is available when the Java application uses the DriverManager class to
obtain a JDBC connection. The connection pool size is determined by the
maxPoolSize property value
and
minPoolSize property value.
The JDBC/MX driver has a connection-pool manager for a combination of catalog and schema;
therefore, connections with the same catalog and schema combinations are pooled together. The
connection pooling property values that are used at the time of obtaining the first connection for a
given catalog and schema combination is effective throughout the life of the process. An application
cannot change these property values subsequent to the first connection for a given catalog and