IBM DB2 Manual page 235

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
| |
|
|
|
|
|
enableRowsetSupport
Specifies whether the IBM Data Server Driver for JDBC and SQLJ uses
multiple-row FETCH for forward-only cursors or scrollable cursors, if the data
source supports multiple-row FETCH. The data type of this property is int.
When enableRowsetSupport is set, its value overrides the useRowsetCursor
property value.
Possible values are:
com.ibm.db2.jcc.DB2BaseDataSource.YES (1)
Specifies that:
v For IBM Data Server Driver for JDBC and SQLJ type 2 connectivity
to DB2 for z/OS, multiple-row FETCH is used for scrollable cursors
and forward-only cursors, if the data source supports multiple-row
FETCH.
v For IBM Data Server Driver for JDBC and SQLJ type 4 connectivity,
or IBM Data Server Driver for JDBC and SQLJ type 2 connectivity to
DB2 Database for Linux, UNIX, and Windows, multiple-row fetch is
used for scrollable cursors, if the data source supports multiple-row
FETCH.
com.ibm.db2.jcc.DB2BaseDataSource.NO (2)
Specifies that multiple-row fetch is not used.
com.ibm.db2.jcc.DB2BaseDataSource.NOT_SET (0)
Specifies that if the enableRowsetSupport property is not set:
v For IBM Data Server Driver for JDBC and SQLJ type 2 connectivity
to DB2 for z/OS, multiple-row fetch is not used.
v For IBM Data Server Driver for JDBC and SQLJ type 4 connectivity,
or IBM Data Server Driver for JDBC and SQLJ type 2 connectivity to
DB2 Database for Linux, UNIX, and Windows, the useRowsetCursor
property determines whether multiple-row fetch is used for
scrollable cursors.
For IBM Data Server Driver for JDBC and SQLJ type 2 connectivity to DB2 for
z/OS, multiple-row fetch is not compatible with progressive streaming.
Therefore, if progressive streaming is used for a FETCH operation,
multiple-row FETCH is not used.
encryptionAlgorithm
Specifies whether the IBM Data Server Driver for JDBC and SQLJ uses 56-bit
DES (weak) encryption or 256-bit AES (strong) encryption. The data type of
this property is int. Possible values are:
The driver uses 56-bit DES encryption.
1
The driver uses 256-bit AES encryption, if the database server supports
2
it. 256-bit AES encryption is available for IBM Data Server Driver for
JDBC and SQLJ type 4 connectivity only.
encryptionAlgorithm can be specified only if the securityMechanism value is
ENCRYPTED_PASSWORD_SECURITY (7) or ENCRYPTED_USER_AND_PASSWORD_SECURITY
(9).
fullyMaterializeInputStreams
Indicates whether streams are fully materialized before they are sent from the
client to a data source. The data type of this property is boolean. The default is
false.
Chapter 7. JDBC and SQLJ reference information
219