JDBC Type 4 Driver Programmer's Reference for SQL/MX Release 3.2.1

The serverDataSource allows the application to set SQL/MX properties (such as resource
governing) for server-side data sources. For more information about server-side data sources, see
"Server Data Sources" in the HP NonStop Connectivity Service Manual for SQL/MX Release 3.2.1.
• If not specified, the default server data source is used.
• If the data source named in serverDataSource is not available on the MXCS server, the
default server data source is used.
• If the data source named in serverDataSource is not started on the MXCS server, an
SQLException is thrown.
Data type: String
Default: None (This value is treated as the default server data source.)
For example, the MXCS server default serverDataSource value is:
serverDataSource=MyDataSource
For more information about the default server data source, see the HP NonStop Connectivity Service
Manual for SQL/MX Release 3.2.1.
T4LogFile
The T4LogFile property sets the name of the logging file for the Type 4 driver.
Set this property on a DataSource object, ConnectionPoolDataSource object, or
DriverManager object.
Data type: String
Default file name is defined by the following pattern:
%h/t4sqlmx%u.log
where
/ represents the local pathname separator.
%h represents the value of the user.home system property.
%u represents a unique number to resolve conflicts.
Any valid file name for your system is allowed.
If you explicitly specify a log file, that file is overwritten each time a FileHandler is established
using that file name.
To retain previously created log files, use the standard java.util.logging file syntax to append
a unique number onto each log file. For example, you can have the following property in a data
source:
T4LogFile = C:/temp/MyLogFile%u.log
That name causes the Type 4 driver to create a new log file using a unique name for each
connection made through that data source. For example:
C:/temp/MyLogFile43289.log
C:/temp/MyLogFile87634.log
C:/temp/MyLogFile27794.log
If you explicitly specify a log file that is not fully qualified, the Type 4 driver creates the file in the
current working directory, for example, in the directory from which the JVM was invoked.
For detailed information about java.util.logging, see the logging summary at:
http://download.oracle.com/javase/1.5.0/docs/api/java/util/logging/package-summary.html
48 Type 4 Driver Properties