JDBC Type 4 Driver 1.1 Programmer's Reference

command line:
-Dt4sqlmx.T4LogLevel=FINE
T4LogLevel Considerations
If a security manager is defined by your application using an AppServer,
LoggingPermission must be 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.
●
translationVerification Property
The translationVerification property defines the behavior of the driver if the driver
cannot translate all or part of an SQL statement or SQL parameter.
Set this property on a DataSource object, ConnectionPoolDataSource object, or
DriverManager object. For information about how to set properties, see How to Specify
JDBC Type 4 Properties.
The value can be TRUE or FALSE.
Data type: String
Default: FALSE
If the translationVerification property’s value is FALSE, and the driver is unable to
translate all or part of an SQL statement; the translation is unspecified. In most cases, the
characters that are untranslatable are encoded as ISO88591 single-byte question marks (? or
0x3F). No exception or warning is thrown.
If the translationVerification property’s value is TRUE and the driver cannot
translation all or part of an SQL statement or parameter, the driver throws an SQLException
with the following text.
Translation of parameter to {0} failed. Cause: {1}
where {0} is replaced with the target character set and {1} is replaced with the cause of the
translation failure.
If the translationVerification property is set to TRUE, the process can use
significantly more system resources. For better performance, set this property to FALSE.