JDBC Driver for SQL/MX Programmer's Reference

internal
Specifies that transactions are always performed within a JDBC/MX driver-managed
transaction. If an external transaction exists when internal transaction mode is in effect, the
external transaction is suspended and the SQL statement is executed within a JDBC/MX
driver-managed transaction. Upon completion of the drivers internally managed transaction,
the existing external transaction is resumed. The Connection autoCommit flag maintains a
value of true when in internal transaction mode.
mixed
Specifies that if an external transaction exists, transactions are always performed within the
external transaction; otherwise, the SQL statement is executed without a transaction. This
mode allows SQL operations that do not require a transaction to be executed without a
transaction, thereby, providing a performance improvement. An SQL exception is thrown if an
SQL command that requires being performed within a transaction is issued when in external
transaction mode and no external transaction exists.
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.
Setting Properties in the Command Line
JDBC/MX driver property names used on the command line in the java -D option must include
the prefix:
jdbcmx.
This notation, which includes the period (.), ensures that all the JDBC/MX driver property names
are unique for a Java application. For example: the maxStatements property becomes
jdbcmx.maxStatements
JDBC/MX Driver Properties Allowed in the Command Line
JDBC/MX
Prefix
Property Name Description