JDBC Type 2 Driver 3.0 Programmer's Reference (SQL/MX 3.x)

schema combination.
As in the basic DataSource object implementation, a Java application can enable statement pooling by
setting the property to a non-zero positive value.
Connection Using the DataSource Interface
The DataSource interface, introduced in the JDBC 2.0 optional package, is the preferred way to establish a
connection to the database because it enhances the application portability. The JDBC/MX driver implements
the
DataSource interface and returns a connection object when an application requests a connection using
the
getConnection method in the DataSource interface.
Using a
DataSource object increases the application portability by allowing the application to use a logical
name for a data source instead of providing driver-specific information in the application. A logical name is
mapped to a
DataSource object by means of a naming service that uses the Java Naming and Directory
Interface (JNDI).
The following table describes the properties that you can use to identify a JDBC/MX data source object:
DataSource Object Properties
Property Name Type Value Description
contBatchOnError
String
on or off
Communicates with JDBC
driver to continue the
remaining jobs in the batch
even after any
BatchUpdateExceptions. See
contBatchOnError Property
.
catalog String
See Default
Catalog and
Schema.
If the default catalog and
schema are not specified, the
JDBC/MX driver allows
SQL/MX to follow its own rules
for defaults.
schema String
See Default
Catalog and
Schema.
See
catalog above.
dataSourceName String
The registered
ConnectionPoolDataSource
name. When this string is
empty, connection pooling is
used by default with the pool
size determined by the
maxPoolSize property and
minPoolSize property of the
basic
DataSource object. For
more information, see
Connection Using the Basic
DataSource API.
description String
Any valid identifier
The description of the data
source.
Enables logging of SQL