IBM DB2 Manual page 230

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
214
Application Programming Guide and Reference for Java
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_DRIVER_CONFIGURATION (X'10')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_CONNECTS (X'20')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_DRDA_FLOWS (X'40')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_RESULT_SET_META_DATA (X'80')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_PARAMETER_META_DATA (X'100')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_DIAGNOSTICS (X'200')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_SQLJ (X'400')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_META_CALLS (X'2000')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_DATASOURCE_CALLS (X'4000')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_LARGE_OBJECT_CALLS (X'8000')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_T2ZOS (X'10000')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_SYSTEM_MONITOR (X'20000')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_TRACEPOINTS () (X'40000')
v com.ibm.db2.jcc.DB2BaseDataSource.TRACE_ALL (X'FFFFFFFF')
To specify more than one trace, use one of these techniques:
v Use bitwise OR (|) operators with two or more trace values. For example, to
trace DRDA flows and connection calls, specify this value for traceLevel:
TRACE_DRDA_FLOWS|TRACE_CONNECTION_CALLS
v Use a bitwise complement (~) operator with a trace value to specify all
except a certain trace. For example, to trace everything except DRDA flows,
specify this value for traceLevel:
~TRACE_DRDA_FLOWS
user
The user ID to use for establishing connections. The data type of this property
is String. When you use the DataSource interface to establish a connection, you
can override this property value by invoking this form of the
DataSource.getConnection method:
getConnection(user, password);
xaNetworkOptimization
Specifies whether XA network optimization is enabled for IBM Data Server
Driver for JDBC and SQLJ type 4 connectivity. You might need to disable XA
network optimization in an environment in which an XA Start and XA End are
issued from one Java process, and an XA Prepare and an XA Commit are
issued from another Java process. With XA network optimization, the XA
Prepare can reach the data source before the XA End, which results in an
XAER_PROTO error. To prevent the XAER_PROTO error, disable XA network
optimization.
The default is true, which means that XA network optimization is enabled. If
xaNetworkOptimization is false, which means that XA network optimization
is disabled, the driver closes any open cursors at XA End time.
xaNetworkOptimization can be set on a DataSource object, or in the url
parameter in a getConnection call. The value of xaNetworkOptimization
cannot be changed after a connection is obtained.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource.maxStatements
Controls an internal statement cache that is associated with a
PooledConnection. The data type of this property is int. Possible values are:
positive integer
Enables the internal statement cache for a PooledConnection, and
specifies the number of statements that the IBM Data Server Driver for
JDBC and SQLJ keeps open in the cache.
™