Description

Specifies whether to hold the cursor across transactions. If this property is set to "true", cursors are not closed when a transaction is committed or rolled back. All resources acquired during the unit of work are held, but locks on specific rows and objects implicitly acquired during the unit of work are released.

Specifies the cursor sensitivity to request from the database. The behavior depends on the resultSetType:

• • ResultSet.TYPE_FORWARD_ONLY or ResultSet.TYPE_SCROLL_SENSITIVE means that the value of this property controls what cursor sensitivity the Java™ program requests from the database.

  • ResultSet.TYPE_SCROLL_INSENSITIVE causes this property to be ignored.

This property is ignored when connecting to systems running V5R1 and earlier versions of i5/OS®.

Specifies the database to use for the connection, including one stored in an independent auxiliary storage pool. This property applies only when connecting to a V5R2 or later version of i5/OS. When you specify a database name, the name must exist in the relational database directory on the server. The following criteria determine which database is accessed:

• • When this property is used to specify a database, the specified database is used. When the specified database does not exist, the connection fails.

  • When this property is used to specify *SYSBAS as the database name, the system default database is used.

  • When this property is omitted, the database name specified in the job description for the user profile is used. When the job description does not specify a database name, the system default database is used.

Specifies one or more libraries that you want to add to or replace the library list of the server job, and optionally sets the default library (default schema).

Library list The server uses specified libraries to resolve unqualified stored procedure names, and stored procedures use them to resolve unqualified names. To specify multiple libraries, use commas or spaces to separate individual entries. You can use *LIBL as a placeholder for the current library list of the server job

• • When the first entry is *LIBL, the specified libraries are added to the current library list of the server job

  • When you do not use *LIBL, the specified libraries replace the current library list of the server job

For more information about library list properties, seeJDBC LibraryList property.

Default schema The server uses the default schema to resolve unqualified names in SQL statements. For example, in the statement "SELECT * FROM MYTABLE", the server looks only in the default schema for MYTABLE. You can specify the default schema on the connection URL. When you do not specify the default schema on the connection URL, the following conditions apply, depending on whether you use SQL Naming or System Naming.

• • SQL Naming When you do not specify the default schema on the connection URL:

Choices

• • "true"

  • "false"

  • "" (Use the ResultSet Type to determine the cursor sensitivity)

  • "asensitive"

  • "sensitive"

  • "insensitive"

Database name "*SYSBAS"

List of server libraries, separated by commas or spaces

• • "31"

  • "63"

"0"-"63"

• • "0"

  • "1"

  • "2"

  • "3"

  • "4"

  • "5"

  • "6"

  • "7"

  • "8"

  • "9"

  • "1200" (UCS-2)

  • "13488" (UTF-16)

  • "true"

  • "false"

Specifies the default transaction isolation.

Specifies how hexadecimal literals are interpreted.

Specifies whether the connection should use true auto commit support. True autocommit means that autocommit is on and is running under a isolation level other than *NONE. By default, the driver handles autocommit by running under the server isolation level of *NONE.

"none"

"read 

uncommited"

"read commited"

"repeatable

read"

"serializable"

• • "character" (Interpret hexadecimal literals as character data)

  • "binary" (Interpret hexadecimal literals as binary data)

  • "true" (Use true autocommit.)

  • "false" (Do not use true autocommit.)

  • "0" = Locks cannot be shared

  • "1" = Locks can be shared

Performance property

"big decimal"

"block criteria"

"block size"

"data compression"

"extended dynamic"

"lazy close"

"lob threshold"

"package"

"package add"

"package cache"

"package criteria"

"package error"

"package library"

"prefetch"

"qaqqinilib"

Description

Specifies whether an intermediate java.math.BigDecimal object is used for packed and zoned decimal conversions. If this property is set to "true", an intermediate java.math.BigDecimal object is used for packed and zoned decimal conversions as described by the JDBC specification. If this property is set to "false", no intermediate objects are used for packed and zoned decimal conversions. Instead, such values are converted directly to and from Java double values. Such conversions will be faster but may not follow all conversion and data truncation rules documented by the JDBC specification.

Specifies the criteria for retrieving data from the server in blocks of records. Specifying a non-zero value for this property will reduce the frequency of communication to the server, and therefore improve performance.

Ensure that record blocking is off if the cursor is going to be used for subsequent UPDATEs, or else the row that is updated will not necessarily be the current row.

Specifies the block size (in kilobytes) to retrieve from the server and cache on the client. This property has no effect unless the "block criteria" property is non-zero. Larger block sizes reduce the frequency of communication to the server, and therefore may improve performance.

Specifies whether result set data is compressed. If this property is set to "true", then result set data is compressed. If this property is set to "false", then result set data is not compressed. Data compression may improve performance when retrieving large result sets.

Specifies whether to use extended dynamic support. Extended dynamic support provides a mechanism for caching dynamic SQL statements on the server. The first time a particular SQL statement is prepared, it is stored in a SQL package on the server. If the package does not exist, it is automatically created. On subsequent prepares of the same SQL statement, the server can skip a significant part of the processing by using information stored in the SQL package. If this is set to "true", then a package name must be set using the "package" property.

Specifies whether to delay closing cursors until subsequent requests. This will improve overall performance by reducing the total number of requests.

Specifies the maximum LOB (large object) size (in bytes) that can be retrieved as part of a result set. LOBs that are larger than this threshold will be retrieved in pieces using extra communication to the server. Larger LOB thresholds will reduce the frequency of communication to the server, but will download more LOB data, even if it is not used. Smaller LOB thresholds may increase frequency of communication to the server, but will only download LOB data as it is needed.

Specifies the base name of the SQL package. Note that only the first seven characters are used to generate the name of the SQL package on the server. This property has no effect unless the "extended dynamic" property is set to "true". In addition, this property must be set if the "extended dynamic" property is set to "true".

Specifies whether to add newly prepared statements to the SQL package specified on the "package" property. This property has no effect unless the "extended dynamic" property is set to "true".

Specifies whether to cache a subset of the SQL package information in client memory. Caching SQL packages locally reduces the amount of communication to the server for prepares and describes. This property has no effect unless the "extended dynamic" property is set to "true".

Specifies the type of SQL statements to be stored in the SQL package. This can be useful to improve the performance of complex join conditions. This property has no effect unless the "extended dynamic" property is set to "true".

Specifies the action to take when SQL package errors occur. When a SQL package error occurs, the driver will optionally throw a SQLException or post a notice to the Connection, based on the value of this property. This property has no effect unless the "extended dynamic" property is set to "true".

Specifies the library for the SQL package. This property has no effect unless the "extended dynamic" property is set to "true".

Specifies whether to prefetch data upon executing a SELECT statement. This will improve performance when accessing the initial rows in the ResultSet.

Specifies a QAQQINI library name. Used to specify the library that contains the qaqqini file to use. A qaqqini file contains all of the attributes that can potentially impact the performance of the DB2® UDB for iSeries™database engine.

"query optimize goal"