This table contains valid data source properties, their values, and their descriptions.
| Set method (data type) | Values | Description |
|---|---|---|
| setAccess(String) | "all", "read call", "read only" | This property can be used to restrict the type of operations that can
be done with a specific connection. The default value is "all" and basically
means that the connection has full access to the Java™ Database Connectivity (JDBC) API.
The "read call" value allows the connection to only perform queries and call stored procedures. An attempt to update the database through an SQL statement causes an SQLException. The "read only" value restricts the connection to only queries. An attempt to process a stored procedure call or update statements causes an SQLException. |
| setBatchStyle(String) | "2.0", "2.1" | The JDBC 2.1 specification defines a second method for how exceptions in a batch update can be handled. The driver can comply with either of these. The default is to work as defined in the JDBC 2.0 specification. |
| setUseBlocking(boolean) | "true", "false" | This property is used to determine whether or not the connection uses
blocking on result set row retrieval. Blocking can significantly improve the
performance of processing result sets. By default, this property is set to true. |
| setBlockSize(int) | "0", "8", "16", "32", "64", "128", "256", "512" | This property indicates the number of rows that are fetched at a time
for a result set. For typical forward only processing of a result set, a block
of this size is obtained if the database has that many rows that satisfy the
query. Only when the end of the block is reached in the JDBC driver's internal
storage, another request for a block of data is sent to the database. This value is only used if the useBlocking property is set to true. Refer to setUseBlocking above for more information. Setting the block size property to "0" has the same effect as calling setUseBlocking(false). The default is to use blocking with a block size of "32". This is a fairly arbitrary decision and the default could change in future releases. Blocking is not used on scrollable result sets. Using blocking affects the degree of cursor sensitivity the user application has. A sensitive cursor sees changes made by other SQL statements. However, because of data caching, changes are only detected when data needs to be fetched from the database. |
| setCursorHold(boolean) | "true", "false" | This property specifies whether or not result sets remain open when
a transaction is committed. A value of true means that an application is able
to access its open result sets after commit is called. A value of false means
that commit closes any open cursors under the connection. By default, this property is set to true. This property serves as a default value for all result sets made for the connection. With cursor support added in JDBC 3.0 (see the ResultSet characteristics section for details), this default is simply replaced if an application specifies different cursor support later. |
| setDataTruncation(boolean) | "true", "false" | This property specifies the following:
|
| setDatabaseName(String) | Any name | This property specifies the database to which the DataSource attempts to connect. The default is *LOCAL. The database name must either exist in the relational database directory on the system that runs the application or be the special value *LOCAL or localhost to specify the local system. |
| setDataSourceName(String) | Any name | This property allows the passing of a ConnectionPoolDataSource Java Naming and Directory Interface (JNDI) name to support connection pooling. |
| setDateFormat(String) | "julian", "mdy", "dmy", "ymd", "usa", "iso", "eur", "jis" | This property allows you to change how dates are formatted. |
| setDateSeparator(String) | "/", "-", ".", ",", "b" | This property allows you to change what the date separator is. This is only valid in combination with some of the dateFormat values (according to system rules). |
| setDecimalSeparator(String) | ".", "," | This property allows you to change what the decimal separator should be. |
| setDescription(String) | Any name | This property allows the setting of this DataSource object's text description. |
| setDoEscapeProcessing(boolean) | "true", "false" | This property specifies whether SQL statements have escaped processing
done on them. The default value for this property is true. |
| setFullErrors(boolean) | "true", "false" | This property allows second-level error text of the full system to be returned in SQLException object messages. The default is false. |
| setLibraries(String) | A space-separated list of libraries | This property allows a list of libraries to be placed into the server job's library list. This property is only used when setSystemNaming(true) is used. |
| setLobThreshold(int) | Any value under 500000 | This property tells the driver to place the actual values instead of Locator OBject (LOB) locators if the LOB column is smaller than the threshold size. |
| setLoginTimeout(int) | Any value | This property is currently ignored and is planned for future use. |
| setNetworkProtocol(int) | Any value | This property is currently ignored and is planned for future use. |
| setPassword(String) | Any string | This property allows for a password to be specified for the connection. This property is ignored if a user ID is not set. |
| setPortNumber(int) | Any value | This property is currently ignored and is planned for future use. |
| setPrefetch(boolean) | "true", "false" | This property specifies whether the driver fetchs the first data for a result set immediately after processing or waits until the data is requested. The default is true. |
| setReuseObjects(boolean) | "true", "false" | This property specifies whether the driver attempts to reuse some types of objects after you close them. This is a performance enhancement. The default is true. |
| setServerName(String) | Any name | This property is currently ignored and is planned for future use. |
| setServerTraceCategories(int) | A string representation of an integer | This property enables tracing of the JDBC server job. If server tracing
is enabled, tracing starts when the client connects to the server, and ends
when the connection is disconnected. Trace data is collected in spooled files on the server. Multiple levels of server tracing can be turned on in combination by adding the constants and passing that sum on the set method. Note: This
property is typically used by support personnel and its values are not discussed
further.
|
| setSystemNaming(boolean) | "true", "false" | This property allows specifying whether collections and tables are separated by a period (SQL naming) or a slash (system naming). This property also determines whether a default library is used (SQL naming) or the library list is used (system naming). The default is SQL naming. |
| setTimeFormat(String) | "hms", "usa", "iso", "eur", "jis" | This property allows you to change how time values are formatted. |
| setTimeSeparator(String) | ":", ".", ",", "b" | This property allows you to change what the time separator is. This is only valid in combination with some of the timeFormat values (according to system rules). |
| setTrace(boolean) | "true", "false" | This property can enable a simple trace. The default value is false. |
| setTransactionIsolationLevel(String) | "none", "read committed", "read uncommitted", "repeatable read", "serializable" | This property allows the specification of the transaction isolation level. The default value for this property is "none", as JDBC defaults to auto-commit mode. |
| setTranslateBinary(Boolean) | "true", "false" | This property can be used to force the JDBC driver to treat binary
and varbinary data values as if they were char and varchar data values. The default for this property is false. |
| setUseBlockInsert(boolean) | "true", "false" | This property allows the native JDBC driver to go into a block insert
mode for inserting blocks of data into the database. This is an optimized
version of the batch update. This optimized mode can only be used in applications
that ensure that they do not break certain system constraints or data insert
failures and potentially corrupt data. Applications that turn on this property only connect to the local system when attempting to perform batched updates. They do not use DRDA® to establish remote connections because a blocked insert cannot be managed over DRDA. Applications must also ensure that PreparedStatements with an SQL insert statement and a values clause make all the insert values parameters. No constants are permitted in the values list. This is a requirement of the blocked insert engine of the system. The default is false. |
| setUser(String) | anything | This property allows the setting of a user ID for obtaining connections. This property requires that you also set the password property. |