Some settings used by the native JDBC driver cannot be set using a connection property. These settings must be set for the JVM in which the native JDBC driver is running. These settings are used for all connections created by the native JDBC driver.
The native driver recognizes the following JVM properties:
| Property | Values | Meaning |
|---|---|---|
| jdbc.db2.job.sort.sequence | default value = *HEX | Setting this property to true causes the native JDBC driver to use the Job Sort Sequence of the user that starts the job instead of using the default value of *HEX. Setting it to anything else or leaving it unset will cause JDBC to continue to use the default of *HEX. Take careful note of what this means. When JDBC connections pass in different user profiles on connection requests, the sort sequence of the user profile that starts the server is used for all of the connections. This is an environment attribute that is set at startup time, not a dynamic connection attribute. |
| jdbc.db2.trace | 1 or error = Trace error information 2 or info = Trace information and error information 3 or verbose = Trace verbose, information, and error information 4 or all or true = Trace all possible information | This property turns on tracing for the JDBC driver. It should be used when reporting a problem. |
| jdbc.db2.trace.config | stdout = Trace information is sent to stdout (default value) usrtrc = Trace information is sent to a user trace. The CL command Dump User Trace Buffer (DMPUSRTRC) can be used to obtain the trace information. file://<pathtofile> = Trace information is send to a file. If the file name contains "%j", the "%j" will be replaced by the job name. An example of <pathtofile> is /tmp/jdbc.%j.trace.txt. | This property is used to specify where the output of the trace should go. |