IBM DB2 Manual page 259

|
|
|
|
|
|
|
|
|
|
db2.jcc.defaultSQLState
If db2.jcc.defaultSQLState is specified with no value, the IBM Data
Server Driver for JDBC and SQLJ returns 'FFFFF'.
db2.jcc.defaultSQLState=xxxxx
xxxxx is the value that the IBM Data Server Driver for JDBC and SQLJ
returns when the SQLSTATE value is null. If xxxxx is longer than five
bytes, the driver truncates the value to five bytes. If xxxxx is shorter
than five bytes, the driver pads xxxxx on the right with blanks.
If db2.jcc.defaultSQLState is not specified, the IBM Data Server Driver for
JDBC and SQLJ returns a null SQLSTATE value.
db2.jcc.disableSQLJProfileCaching
Specifies whether serialized profiles are cached when the JVM under which
their application is running is reset. db2.jcc.disableSQLJProfileCaching applies
only to applications that run in a resettable JVM (applications that run in the
CICS, IMS, or Java stored procedure environment), and use IBM Data Server
Driver for JDBC and SQLJ type 2 connectivity on DB2 for z/OS. Possible
values are:
SQLJ serialized profiles are not cached every time the JVM is reset, so
YES
that new versions of the serialized profiles are loaded when the JVM is
reset. Use this option when an application is under development, and
new versions of the application and its serialized profiles are produced
frequently.
NO SQLJ serialized profiles are cached when the JVM is reset. NO is the
default.
db2.jcc.dumpPool
Specifies the types of statistics on global transport pool events that are written,
in addition to summary statistics. The global transport pool is used for the
connection concentrator and Sysplex workload balancing.
db2.jcc.dumpPoolStatisticsOnSchedule and
db2.jcc.dumpPoolStatisticsOnScheduleFile must also be set for writing statistics
before any statistics are written.
You can specify one or more of the following types of statistics with the
db2.jcc.dumpPool property:
v DUMP_REMOVE_OBJECT (hexadecimal: X'01', decimal: 1)
v DUMP_GET_OBJECT (hexadecimal: X'02', decimal: 2)
v DUMP_WAIT_OBJECT (hexadecimal: X'04', decimal: 4)
v DUMP_SET_AVAILABLE_OBJECT (hexadecimal: X'08', decimal: 8)
v DUMP_CREATE_OBJECT (hexadecimal: X'10', decimal: 16)
v DUMP_SYSPLEX_MSG (hexadecimal: X'20', decimal: 32)
v DUMP_POOL_ERROR (hexadecimal: X'80', decimal: 128)
To trace more than one type of event, add the values for the types of events
that you want to trace. For example, suppose that you want to trace
DUMP_GET_OBJECT and DUMP_CREATE_OBJECT events. The numeric
equivalents of these values are 2 and 16, so you specify 18 for the
db2.jcc.dumpPool value.
The default is 0, which means that only summary statistics for the global
transport pool are written.
db2.jcc.dumpPoolStatisticsOnSchedule
Specifies how often, in seconds, global transport pool statistics are written to
Chapter 7. JDBC and SQLJ reference information
243