IBM Data Server Driver for JDBC and SQLJ properties for Db2 for z/OS

Some of the IBM Data Server Driver for JDBC and SQLJ properties apply only to Db2 for z/OS servers.

The following list includes the properties for the IBM Data Server Driver for JDBC and SQLJ:

accountingInterval

Specifies whether Db2 accounting records are produced at commit points or on termination of the physical connection to the data source. The data type of this property is String.

If the value of accountingInterval is "COMMIT", and there are no open, held cursors, Db2 writes an accounting record each time that the application commits work. If the value of accountingInterval is "COMMIT", and the application performs a commit operation while a held cursor is open, the accounting interval spans that commit point. The accounting interval also ends at the next valid accounting interval end point. If the value of accountingInterval is not "COMMIT", accounting records are produced on termination of the physical connection to the data source.

The accountingInterval property sets the accounting-interval parameter for an underlying RRSAF sign-on call. If the value of subsystem parameter ACCUMACC is not NO, the ACCUMACC value overrides the accountingInterval setting.

The accountingInterval property applies only to IBM Data Server Driver for JDBC and SQLJ type 2 connectivity. The accountingInterval property is not applicable to connections under CICS® or IMS, or for Java stored procedures.

The accountingInterval property overrides the db2.jcc.accountingInterval configuration property.

charOutputSize

Specifies the maximum number of bytes to use for INOUT or OUT stored procedure parameters that are registered as Types.CHAR charOutputSize applies only to IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

Because DESCRIBE information for stored procedure INOUT and OUT parameters is not available at run time, by default, the IBM Data Server Driver for JDBC and SQLJ sets the maximum length of each character INOUT or OUT parameter to 32767. For stored procedures with many Types.CHAR parameters, this maximum setting can result in allocation of much more storage than is necessary.

To use storage more efficiently, set charOutputSize to the largest expected length for any Types.CHAR INOUT or OUT parameter.

The charOutputSize property has no effect on INOUT or OUT parameters that are registered as Types.VARCHAR or Types.LONGVARCHAR. The driver uses the default length of 32767 for Types.VARCHAR and Types.LONGVARCHAR parameters.

Before you choose the value for charOutputSize, you need to consider the possibility of expansion during character conversion. Because the IBM Data Server Driver for JDBC and SQLJ has no information about the server-side CCSID that is used for output parameter values, the driver requests the stored procedure output data in UTF-8 Unicode. The charOutputSize value needs to be the maximum number of bytes that are needed after the parameter value is converted to UTF-8 Unicode. UTF-8 Unicode characters can require up to 3 bytes. (The euro symbol is an example of a 3-byte UTF-8 character). To ensure that the value of charOutputSize is large enough, if you have no information about the output data, set charOutputSize to three times the defined length of the largest CHAR parameter.

clientApplcompat

For connections to Db2 12 for z/OS data servers at a function level of V12R1M501 or later, sets the capabilities of a particular instance of the IBM Data Server Driver for JDBC and SQLJ to a function level that is less than or equal to the function level of the data server.

For example, suppose that the driver packages for an instance of the IBM Data Server Driver for JDBC and SQLJ are bound with an APPLCOMPAT value of V12R1M501. Some applications that use that instance of the driver need only the capabilities in function level V12R1M500. You can set clientApplcompat to V12R1M500 for those applications to use only capabilities of the V12R1M500 function level.

If the driver packages have an APPLCOMPAT value of V12R1M500 or less, and clientApplcompat is not set, the APPLCOMPAT setting determines the set of capabilities that the client application can use.

If the driver packages have an APPLCOMPAT value of V12R1M501 or greater, setting clientApplcompat is optional. However, if clientApplcompat is not set, the data server rejects a connection if the IBM Data Server Driver for JDBC and SQLJ is at a level that does not support the APPLCOMPAT bind option value of the Db2 12 for z/OS package.

For more information, see V12R1Mnnn application compatibility levels for data server clients and drivers.

clientProgramId

Specifies a value for the client program ID that can be used to identify the end user. The data type of this property is String, and the length is 80 bytes. If the program ID value is less than 80 bytes, the value must be padded with blanks.

clientProgramName

Specifies an application name that can be used to correlate applications that are being processed by Db2 for z/OS data servers with the names of distributed applications. The data type of this property is String. The maximum length is 20 bytes. If this value is null, the IBM Data Server Driver for JDBC and SQLJ supplies a value of db2jcc_applicationapplication-name, where application-name is the value of the CURRENT CLIENT_APPLNAME special register.

Important: Monitoring of applications with IFCID 411 is limited to 6000 unique application names. If this limit is exceeded, Db2 for z/OS issues message DSNL030I with reason code 00D3105D and stops collecting the statistics for any new application names until DDF is restarted. For best results when monitoring remote user statistics, use the CURRENT CLIENT_CORR_TOKEN special register to identify individual connections.

This property applies only to IBM Data Server Driver for JDBC and SQLJ type 4 connectivity.

clientUser

Specifies the name of the user on whose behalf the application that is using the connection is running. This value is stored in Db2 special register CURRENT CLIENT_USERID. The data type of this property is String. The maximum length is 128 bytes.

A Java empty string ("") is valid for the clientUser value, but the Java null value is not valid.

Important: Monitoring of applications with IFCID 412 is limited to 6000 unique user ID values. If this limit is exceeded, Db2 for z/OS issues message DSNL030I with reason code 00D3105E and stops collecting the statistics for any new application names until DDF is restarted. For best results when monitoring remote user statistics, use the CURRENT CLIENT_CORR_TOKEN special register to identify individual connections.

clientWorkstation

Specifies the host name of the computer on which the application that is using the connection is running. This value is stored in Db2 special register CURRENT CLIENT_WRKSTNNAME. The data type of this property is String. The maximum length is 255 bytes.

Starting with version 3.68 or 4.18 of the IBM Data Server Driver for JDBC and SQLJ, if clientWorkstation is set to any value other than an IP address, no value is sent to the data server.

currentLocaleLcCtype

Specifies the LC_CTYPE locale that is used to execute SQL statements that use a built-in function that references a locale. The data type of this property is String. If currentLocaleLcCtype is set, the IBM Data Server Driver for JDBC and SQLJ sets the CURRENT LOCALE LC_CTYPE special register on the data server to the property value. The currentLocaleLcCtype property has no default.

The currentLocaleLcCtype property can be set only at the start of a connection, and cannot be changed while the connection is active.

currentSQLID

The currentSQLID property specifies the following information:

The authorization ID that is used for authorization checking on dynamically prepared CREATE, GRANT, and REVOKE SQL statements.
The owner of a table space, database, storage group, or synonym that is created by a dynamically issued CREATE statement.
The implicit qualifier of all table, view, alias, and index names specified in dynamic SQL statements.

The currentSQLID property sets the value in the CURRENT SQLID special register on a Db2 for z/OS server. If the currentSQLID property is not set, the default schema name is the value in the CURRENT SQLID special register.

enableMultiRowInsertSupport

Specifies whether the IBM Data Server Driver for JDBC and SQLJ uses multi-row INSERT for batched INSERT or MERGE operations, when the target data server is a Db2 for z/OS server that supports multi-row INSERT. The batch operations must be PreparedStatement calls with parameter markers. The data type of this property is Boolean. The default is true.

The enableMultiRowInsertSupport value cannot be changed during a connection. The enableMultiRowInsertSupport property must be set to false if INSERT FROM SELECT statements are executed in a batch. Otherwise, the driver produces a BatchUpdateException error.

enableSeamlessFailoverErrorCodes

Specifies whether the IBM Data Server Driver for JDBC and SQLJ maps seamless error codes, such as -4498, -30108, or -20542, to communication error code -4499. The data type of this property is Boolean. Possible values are:

true: The IBM Data Server Driver for JDBC and SQLJ does not map seamless errors to communication error code -4499. The application receives different error codes, depending on the types of errors that occurred.
false: The IBM Data Server Driver for JDBC and SQLJ maps seamless errors to communication error code -4499. If a seamless error occurs during execution of an application, the driver throws an exception with error code -4499. false is the default.

enableSeamlessFailoverErrorCodes applies to IBM Data Server Driver for JDBC and SQLJ type 4 connectivity to Db2 for z/OS only.

enableT2zosLBF

Specifies whether limited block fetch is used for connections that use IBM Data Server Driver for JDBC and SQLJ type 2 connectivity to retrieve data from a table on a local Db2 for z/OS data server. The data type of this property is an int. You must use one of the following possible values of the property:

com.ibm.db2.jcc.DB2BaseDataSource.NOT_SET (0) or not specified

This value is the default setting.

For a connection to a Db2 for z/OS data server in Version 10 conversion mode, specifies that limited block fetch is not used for retrieving data from a local table that uses the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.
For a connection to a Db2 for z/OS data server in Version 10 new-function mode or later, specifies that limited block fetch is used for retrieving data from a local table that uses the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

com.ibm.db2.jcc.DB2BaseDataSource.YES (1)

Specifies that limited block fetch is used for retrieving data from a local table that uses the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

If you set this property to 1, and IBM Db2 Analytics Accelerator for z/OS might also need to be switched on during cursor reuse, you need to set configuration property db2.jcc.enableT2zosLBFSwitchWithIDAA to 1.

com.ibm.db2.jcc.DB2BaseDataSource.NO (2)

Specifies that limited block fetch is not used for retrieving data from a local table that uses the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

The enableT2zosLBF property applies to Db2 for z/OS data servers in Version 10 new-function mode or later. The enableT2zosLBF property does not apply to retrieval of stored procedure result sets.

enableT2zosLBFSPResultSets

Specifies whether limited block fetch is used for connections that use IBM Data Server Driver for JDBC and SQLJ type 2 connectivity to retrieve data from a stored procedure result set on a local Db2 for z/OS data server. The data type of this property is int. The following are possible values of the property:

com.ibm.db2.jcc.DB2BaseDataSource.YES (1) or com.ibm.db2.jcc.DB2BaseDataSource.NOT_SET (0): Specifies that limited block fetch is used for retrieving data from a stored procedure result set that uses the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity. This value is the default.
com.ibm.db2.jcc.DB2BaseDataSource.NO (2): Specifies that limited block fetch is not used for retrieving data from a stored procedure result set that uses the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

The enableT2zosLBFSPResultSets property applies to Db2 for z/OS data servers in Version 10 new-function mode or later.

enableXACleanTransaction

Specifies whether to reset session data at XA End. The data type of enableXACleanTransaction is Boolean. Possible values of the property include the following Boolean values:

true: Enables clean transaction mode. All database resources such as cursors and DGTTs, are implicitly closed and dropped on XA_END.
false: Enable dirty transaction mode. This value is the default. Session data is not reset at XA End, and persists across transactions.

extendedTableInfo

The extendedTableInfo property specifies whether information about extended table types is returned from a DatabaseMetaData.getTables method call. Currently, there exists one extended table type: ACCEL-ONLY TABLE.

com.ibm.db2.jcc.DB2BaseDataSource.NO (2) or com.ibm.db2.jcc.DB2BaseDataSource.NOT_SET (0)

The result set that is returned by the DatabaseMetaData.getTables method does not contain columns for extended table types.

Rows for extended table types are returned only if "TABLE" is explicitly specified in the types parameter value. In this case, extended table types are listed as TABLE in the TABLE_TYPE column of the result set.

com.ibm.db2.jcc.DB2BaseDataSource.YES (1)

The result set that is returned by the DatabaseMetaData.getTables method contains rows and columns for extended table types. The following list depicts the result set in more detail:

The result set contains these extra columns after the columns that are always returned in the result set from DatabaseMetaData.getTables:

Table 1. Extra columns returned by DatabaseMetaData.getTables
Column Name	Data type	Description
TEMPORAL_TABLE_TYPE	String	Contains the type of temporal table. The following shows possible values of the temporal table: SYSTEM System-period temporal table. APPLICATION Application-period temporal table. BITEMPORAL Bitemporal table. Empty string Not a temporal table. This row is returned for connections to Db2 for z/OS Version 10 or later.
IS_ACCELERATED	String	Indicates whether the table is an accelerated table. Possible values are YES or NO. This row is returned for connections to Db2 for z/OS Version 10 or later.
ACCEL_ARCHIVE_STATUS	String	Contains the archive status of the table in the accelerator database. See the description of the ARCHIVE column in SYSACCEL.SYSACCELERATEDTABLES table for the possible values and their meanings. This row is returned for connections to Db2 for z/OS Version 10 or later.
IS_ARCHIVE_ENABLED	String	Indicates whether the table is an archive-enabled table. Possible values are YES or NO. This row is returned for connections to Db2 for z/OS Version 11 or later.

Rows for extended table types are returned under the following circumstances:
- All table types are implicitly requested by specifying null in the types parameter value.
- An extended table type name is explicitly specified in the types parameter value.
  In this case, the extended table type is listed by its extended table type name in the TABLE_TYPE column of the result set.

jdbcCollection

Specifies the collection ID for the packages that are used by an instance of the IBM Data Server Driver for JDBC and SQLJ at run time. The data type of jdbcCollection is String. The default is NULLID.

This property is used with the DB2Binder -collection option. The DB2Binder utility must contain bounded IBM Data Server Driver for JDBC and SQLJ packages at the server by using a -collection value that matches the jdbcCollection value.

The jdbcCollection setting does not determine the collection that is used for SQLJ applications. For SQLJ, the collection is determined by the -collection option of the SQLJ customizer.

The jdbcCollection setting does not apply to IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

keyUsage

The keyUsage property is used only for client certificate selection of keyUsage-based certificates from the WINDOWS-MY keystore type. The PKI Card supports the WINDOWS-MY keystore type and WINDOWS-ROOT truststore type. It does not apply on the server certificate for server certificate authentication. If dataSource or Connection is configured with the securityMechanism, TLS_CLIENT_CERTIFICATE_SECURITY, then keyUsage is applied on the Connection object to select the client certificate.

If dataSource or Connection is not configured with the securityMechanism, TLS_CLIENT_CERTIFICATE_SECURITY, the JCC driver ignores the keyUsage property and proceeds with the default settings for an SSL connection. For possible values of the keyUsage property, see the following table.

Table 2. keyUsage constants
Certificate keyUsage constant	Values
`com.ibm.db2.jcc.DB2BaseDataSource.NOT_SET`	0
`com.ibm.db2.jcc.DB2BaseDataSource.digitalSignature`	1
`com.ibm.db2.jcc.DB2BaseDataSource.nonRepudiation`	2
`com.ibm.db2.jcc.DB2BaseDataSource.keyEncipherment`	4
`com.ibm.db2.jcc.DB2BaseDataSource.dataEncipherment`	8
`com.ibm.db2.jcc.DB2BaseDataSource.keyAgreement`	16
`com.ibm.db2.jcc.DB2BaseDataSource.keyCertSign`	32
`com.ibm.db2.jcc.DB2BaseDataSource.cRLSign`	64
`com.ibm.db2.jcc.DB2BaseDataSource.encipherOnly`	128
`com.ibm.db2.jcc.DB2BaseDataSource.decipherOnly`	256

The default value of this integer property is 0 (NOT SET). The keyUsage constants (other than KeyUsage_ALL, -1) are numerically additive. To specify multiple keyUsage components (as specified by their corresponding keyUsage constants) in the keyUsage property, combine the preferred keyUsage constants by using numeric addition. For example, suppose that this trace specification is needed:

(digitalSignature |
 nonRepudiation |
 keyEncipherment | 
 dataEncipherment | 
 keyAgreement | 
 cRLSign)

You need to set keyUsage to the sum of the integer values of these constants:

1 + 2 + 4 + 16 + 32 + 64 = 119

. Therefore, keyUsage must be set to 119 to enable these keyUsage components.

maxConnCachedParamBufferSize

Specifies the maximum size of an internal buffer that is used for caching input parameter values for PreparedStatement objects. The buffer caches values on the native code side that are passed from the driver's Java code side for the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity. The buffer is used by all PreparedStatement objects for a Connection. The default is 1048576 (1 MB). The default value must be adequate for most users. Set maxConnCachedParamBufferSize to a larger value if many applications that run under the driver instance have PreparedStatement objects with large numbers of input parameters or large input parameters. The maxConnCachedParamBufferSize value must be larger than the maximum size of all input parameter data for a Connection. However, you also need to consider the total number of connections and the maximum amount of memory that is available when you set the maxConnCachedParamBufferSize value.

The buffer exists for the life of a Connection, unless it reaches the maximum size. If that happens, the buffer is freed on each call to the native code. The corresponding buffer on the Java code side is freed on PreparedStatement.clearParameters and PreparedStatement.close calls. The buffers are not cleared if an application calls PreparedStatement.clearParameters, and the buffers do not reach the maximum size.

maxRowsetSize

Specifies the maximum number of bytes that are used for rowset buffering for each statement, when the IBM Data Server Driver for JDBC and SQLJ uses multiple-row FETCH for cursors. The data type of this property is int. The default is 32767.

The maxRowsetSize property applies only to the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

pkList

Specifies a package list that is used for the underlying RRSAF CREATE THREAD call when a JDBC or SQLJ connection to a data source is established. The pkList property applies only to the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity on Db2 for z/OS.

Specify this property if you do not bind plans for your SQLJ programs or for the JDBC driver. If you specify this property, do not specify planName.

Recommendation: Use pkList instead of planName.

The following is the format of the package list:

The pkList property overrides the value of the db2.jcc.pkList configuration property. If pkList, planName, and db2.jcc.pkList are not specified, then the value of pkList is NULLID.*.

planName

Specifies a Db2 plan name that is used for the underlying RRSAF CREATE THREAD call when a JDBC or SQLJ connection to a data source is established. planName applies only to IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

Specify this property if you bind plans for your SQLJ programs and for the JDBC driver packages. If you specify this property, do not specify pkList.

The planName property overrides the value of the db2.jcc.planName configuration property. If pkList, planName, and db2.jcc.planName are not specified, NULLID.* is used as the package list for the underlying CREATE THREAD call.

queryAcceleration

Specifies the value that is to be used for the CURRENT QUERY ACCELERATION special register. The data type of this property is String. Possible values are:

NONE: Specifies that no query acceleration is done.
ENABLE: Specifies that queries are accelerated only if Db2 for z/OS determines that it is advantageous to do so. If there is an accelerator failure while a query is running, or the accelerator returns an error, Db2 for z/OS returns an SQL error to the application.
ENABLE WITH FAILBACK: Specifies that queries are accelerated only if Db2 for z/OS determines that it is advantageous to do so. If the accelerator returns an error during the PREPARE or first OPEN for the query, Db2 for z/OS executes the query without the accelerator. If the accelerator returns an error during a FETCH or a subsequent OPEN, Db2 for z/OS returns the error to the user, and does not execute the query.
ELIGIBLE: Specifies that queries are accelerated if they are eligible for acceleration. Db2 for z/OS does not use cost information to determine whether to accelerate the queries. Queries that are not eligible for acceleration are executed by Db2 for z/OS. If there is an accelerator failure while a query is running, or the accelerator returns an error, Db2 for z/OS returns an SQL error to the application.
ALL: Specifies that queries are accelerated if they are eligible for acceleration. Db2 for z/OS does not use cost information to determine whether to accelerate the queries. Queries that are not eligible for acceleration are not executed by Db2 for z/OS, and an SQL error is returned. If there is an accelerator failure while a query is running, or the accelerator returns an error, Db2 for z/OS returns an SQL error to the application.

reportLongTypes

Specifies whether DatabaseMetaData methods report LONG VARCHAR and LONG VARGRAPHIC column data types as long data types. The data type of this property is short. Possible values are:

com.ibm.db2.jcc.DB2BaseDataSource.NO (2) or com.ibm.db2.jcc.DB2BaseDataSource.NOT_SET (0): Specifies that DatabaseMetaData methods that return information about a LONG VARCHAR or LONG VARGRAPHIC column return java.sql.Types.VARCHAR in the DATA_TYPE column and VARCHAR or VARGRAPHIC in the TYPE_NAME column of the result set. This value is the default for Db2 for z/OS Version 9 or later.
com.ibm.db2.jcc.DB2BaseDataSource.YES (1): Specifies that DatabaseMetaData methods that return information about a LONG VARCHAR or LONG VARGRAPHIC column return java.sql.Types.LONGVARCHAR in the DATA_TYPE column of the result set. The method also returns a LONG VARCHAR or LONG VARGRAPHIC in the TYPE_NAME column of the result set.

sendCharInputsUTF8

Specifies whether the IBM Data Server Driver for JDBC and SQLJ converts character input data to the CCSID of the Db2 for z/OS database server, or sends the data in UTF-8 encoding for conversion by the database server. sendCharInputsUTF8 applies to IBM Data Server Driver for JDBC and SQLJ type 2 connectivity. The data type of this property is int. If this property is also set at the driver level (db2.jcc.sendCharInputsUTF8), this value overrides the driver-level value.

The following shows possible values of the property:

com.ibm.db2.jcc.DB2BaseDataSource.NO (2)

Specifies that the IBM Data Server Driver for JDBC and SQLJ converts character input data to the target encoding before the data is sent to the Db2 for z/OS database server. com.ibm.db2.jcc.DB2BaseDataSource.NO is the default.

com.ibm.db2.jcc.DB2BaseDataSource.YES (1)

Specifies that the IBM Data Server Driver for JDBC and SQLJ sends character input data to the Db2 for z/OS database server in UTF-8 encoding. The database server converts the data from UTF-8 encoding to the target CCSID.

Specify com.ibm.db2.jcc.DB2BaseDataSource.YES only if conversion to the target CCSID by the SDK for Java causes character conversion problems. The most common problem occurs when you use IBM Data Server Driver for JDBC and SQLJ type 2 connectivity to insert a Unicode line feed character (U+000A) into a table column that has CCSID 37, and then retrieve that data from a non-z/OS client. If the SDK for Java does the conversion during insertion of the character into the column, the line feed character is converted to the EBCDIC new line character X'15'. However, during retrieval, some SDKs for Java on operating systems other than z/OS convert the X'15' character to the Unicode next line character (U+0085) instead of the line feed character (U+000A). The next line character causes unexpected behavior for some XML parsers. If you set sendCharInputsUTF8 to com.ibm.db2.jcc.DB2BaseDataSource.YES, the Db2 for z/OS database server converts the U+000A character to the EBCDIC line feed character X'25' during insertion into the column. Therefore, the character is always retrieved as a line feed character.

Conversion of data to the target CCSID on the database server might cause the IBM Data Server Driver for JDBC and SQLJ to use more memory than conversion by the driver. The driver allocates memory for conversion of character data from the source encoding to the encoding of the data that it sends to the database server. The amount of space that the driver allocates for character data that is sent to a table column is based on the maximum length of the data. UTF-8 data can require up to 3 bytes for each character. Therefore, if the driver sends UTF-8 data to the database server, the driver needs to allocate three times the maximum number of characters in the input data. If the driver does the conversion, and the target CCSID is a single-byte CCSID, the driver needs to allocate only the maximum number of characters in the input data.

sessionTimeZone

Specifies the setting for the CURRENT SESSION TIME ZONE special register. The data type of this property is String.

The sessionTimeZone value is a time zone value that is in the format of sth:tm. The s in the format is the sign, th is the time zone hour, and tm is time zone minutes. The range of valid values is -12:59 to +14:00.

sqljEnableClassLoaderSpecificProfiles

Specifies whether the IBM Data Server Driver for JDBC and SQLJ allows the use and loading of SQLJ profiles with the same Java name in multiple J2EE application (.ear) files. The data type of this property is Boolean. The default is false. The sqljEnableClassLoaderSpecificProfiles property is a dataSource property. This property is primarily intended for use with WebSphere® Application Server.

ssid

Specifies the name of the local Db2 for z/OS subsystem to which a connection is established by using the IBM Data Server Driver for JDBC and SQLJ type 2 connectivity. The data type of this property is String.

The ssid property overrides the db2.jcc.ssid configuration property.

The ssid property can be the subsystem name for a local subsystem or a group attachment name or subgroup attachment name.

Specification of a single local subsystem name allows more than one subsystem on a single LPAR to be accessed as a local subsystem for connections that use IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

Specification of a group attachment name or subgroup attachment name allows failover processing to occur if a data sharing group member fails. If the Db2 subsystem to which an application is connected fails, the connection ends. However, when new connections use that group attachment name or subgroup attachment name, Db2 for z/OS uses group or subgroup attachment processing to find an active Db2 subsystem to which to connect.

The ssid property applies only to IBM Data Server Driver for JDBC and SQLJ type 2 connectivity.

sslKeyStoreLocation

Specifies the full path name of the Java KeyStore on the client that contains the client certificate for an SSL connection. The client certificate is used to identify the client only during mutual authentication or client certificate security.

The IBM Data Server Driver for JDBC and SQLJ uses this option only if the sslConnection property is set to true and securityMechanism is set to 18(TLS_CLIENT_CERTIFICATE_SECURITY).

If sslKeyStoreLocation is set, and sslConnection is set to true, the IBM Data Server Driver for JDBC and SQLJ uses the sslKeyStoreLocation value instead of the value in the javax.net.ssl.keyStore Java property.

The default value for sslKeyStoreLocation is provided by the db2.jcc.sslKeyStoreLocation configuration property. If the db2.jcc.sslKeyStoreLocation configuration property is also not specified, then the default value for sslKeyStoreLocation is null.

This property is applicable only to IBM Data Server Driver for JDBC and SQLJ type 4 connectivity.

sslKeyStorePassword

Specifies the password for the Java KeyStore on the client that contains the client certificate for an SSL connection.

The IBM Data Server Driver for JDBC and SQLJ uses this option only if the sslConnection property is set to true and securityMechanism is set to 18(TLS_CLIENT_CERTIFICATE_SECURITY).

If sslKeyStorePassword is set, and sslConnection is set to true, the IBM Data Server Driver for JDBC and SQLJ uses the sslKeyStorePassword value instead of the value in the javax.net.ssl.keyStorePassword Java property.

The default value for sslKeyStorePassword is provided by the db2.jcc.sslKeyStorePassword configuration property. If the db2.jcc.sslKeyStorePassword configuration property is also not specified, then the default value for sslKeyStorePassword is null.

This property is applicable only to IBM Data Server Driver for JDBC and SQLJ type 4 connectivity.

sslKeyStoreType

Specifies the type of the Java KeyStore on the client that contains the client certificate for an SSL connection.

The IBM Data Server Driver for JDBC and SQLJ uses this option only if the sslConnection property is set to true and securityMechanism is set to 18(TLS_CLIENT_CERTIFICATE_SECURITY).

If sslKeyStoreType is set, and sslConnection is set to true, the IBM Data Server Driver for JDBC and SQLJ uses the sslKeyStoreType value instead of the value in the javax.net.ssl.keyStoreType Java property.

The default value for sslKeyStoreType is provided by the db2.jcc.sslKeyStoreType configuration property. If the db2.jcc.sslKeyStoreTypeconfiguration property is also not specified, then the default value for sslKeyStoreType is null.

This property is applicable only to IBM Data Server Driver for JDBC and SQLJ type 4 connectivity.

useRowsetCursor

Specifies whether the IBM Data Server Driver for JDBC and SQLJ always uses multiple-row FETCH for scrollable cursors if the data source supports multiple-row FETCH. The data type of this property is Boolean.

This property applies only to IBM Data Server Driver for JDBC and SQLJ type 4 connectivity, or to IBM Data Server Driver for JDBC and SQLJ type 2 connectivity. If the enableRowsetSupport property is not set, the default for useRowsetCursor is true. If the enableRowsetSupport property is set, the useRowsetCursor property is not used.

Applications that use the JDBC 1 technique for performing positioned update or delete operations must set useRowSetCursor to false. Those applications do not operate properly if the IBM Data Server Driver for JDBC and SQLJ uses multiple-row FETCH.