JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2 (H06.25+, J06.14+)

INFO
provides informational messages, typically about connection pooling, statement pooling, and
resource usage. This information can help in tuning application performance.
CONFIG
provides static configuration messages that can include property values and other Type 4 driver
configuration information.
FINE
provides tracing information from the Type 4 driver methods described in the Type 4 driver
API. The level of tracing is equivalent to the level of tracing provided when calling the
setLogWriter() method of the DriverManager class or the DataSource class.
FINER
indicates a detailed tracing message for which internal Type 4 driver methods provide messages.
These messages can be useful in debugging the Type 4 driver.
FINEST
indicates a highly detailed tracing message. The driver provides detailed internal data messages
that can be useful in debugging the Type 4 driver.
ALL
logs all messages.
For example, to enable tracing, use the t4sqlmx.T4LogLevel property specified in the command
line:
-Dt4sqlmx.T4LogLevel=FINE
T4LogLevel Considerations
• If a security manager is defined by your application using an AppServer,
LoggingPermission must be granted in the java.policy file as follows:
permission java.util.logging.LoggingPermission "control","";
• The Type 4 driver is not designed to inherit the java.util.logging.FileHandler.level
settings at program startup.
• Server-side tracing and logging through MXCS is managed by NSM/web. For more information
about server side-tracing (logging), see the NSM/web online help.
T4QueryExecuteLogFile
Whenever the queryExecuteTime is specified, T4QueryExecuteLogFile property is used
to set the name of the logging file for the queryExecuteTime property.
Set this property on a DataSource object, ConnectionPoolDataSource object, or a
DriverManager object.
Data type: String
The default log file name is t4sqlmxQueryExecuteTime.log and will be created
in the user.home directory.
The system can accept any valid file name. If a log file is specified explicitly, it is overwritten each
time a FileHandler is established using that filename.
If a log file that is not fully qualified is specified explicitly, the Type 4 driver creates the file in the
current working directory, for example, in the directory from where the JVM was invoked.
translationVerification
The translationVerification property defines the behavior of the driver if the driver cannot
translate all or part of an SQL statement or SQL parameter.
50 Type 4 Driver Properties