JDBC Type 2 Driver Programmer's Reference for SQL/MX Release 3.2.1 (H06.26+, J06.15+)

mixed
Specifies that the driver inherits any active transaction in the current thread. The
autocommit setting of the transaction is ignored. The application must either commit
or rollback the transaction in this mode. If there is no active transaction, the driver
creates one and begins the transaction, or aborts it if there is an SQL error. In this
mode, the driver supports both autocommit and non-autocommit. The application
ends the transaction in non-autocommit mode.
external
Specifies that if an external transaction exists, transactions are performed within the external
transaction. If an external transaction does not exist, the SQL statement is executed without a
transaction. This allows SQL statements that do not require an existing transaction to be performed
without one, providing an improvement in performance. If an SQL command requires a transaction
and no external transaction exists, an SQL exception is thrown.
NOTE: Using external transactionMode for SQL statements that require execution within a
transaction results in an SQL exception. Therefore, do not specify external transactionMode
under these conditions.
Considerations:
• If any other string is specified for the value of transaction mode, mixed is used.
• Using the external or mixed transaction mode can improve performance.
• Using the internal transaction mode can affect performance for applications because of the
overhead of TMF transactions under a heavy load.
• This property can be set within a JDBC/MX driver properties file, defined within a DataSource
object, or passed in through the java command line.
• The transaction mode can only be changed for new connections; therefore, it cannot be
dynamically changed within a connection.
This property can be specified in a data source, in the JDBC/MX properties file, or in the java
command line.
queryExecuteTime Property
You can use the queryExecuteTime property to specify the query execution time, in milliseconds.
Any query that exceeds the specified time will be logged in the log file. If you configure this
property, a separate log file is created. You must set this property on a DataSource object,
ConnectionPoolDataSource object, or a DriverManager object.
You must consider the following settings while configuring the queryExecuteTime property:
• Data type — long
• Units — milliseconds
• Default — 0
• Range — 1 to 9,223,372,036,854,775,807 (2**63-1))
In the following example, the value of queryExecuteTime is set to 10 milliseconds:
java -Djdbcmx.queryExecuteTime=10
For information on configuring a log file, see “T2QueryExecuteLogFile Property” (page 31).
For information on setting properties, see “Setting Properties in the Command Line” (page 31).
30 Accessing SQL Databases with SQL/MX