JDBC Type 4 Driver 1.1 Programmer's Reference

4 Driver Logging). The Type 4 Driver Logging provides the same level of logging and tracing as the standard JDBC tracing
and logging facility with the following additional information:
More detail about the internals of the Type 4 driver and internal tracing information●
Type 4 driver performance-tuning information●
Finer control over the amount and type of logging information●
Error and warning messages●
Accessing the Type 4 Driver Logging Facility
The Type 4 Driver Logging facility is based on the java.util.logging package. The Type 4 driver instantiates a
java.util.logging.Logger class and names the logger com.tandem.t4jdbc.logger.
Your JDBC program can access the Type 4 driver logger directly by calling the java.util.logging.Logger static
method getLogger(String). For example
String t4Logger = java.util.logging.Logger.getLogger(“com.tandem.t4jdbc.logger”);
Controlling Type 4 Driver Logging Output
The Type 4 driver provides two properties that you can use to control logging output.
T4LogLevel—specifies the level of logging. For information about using this property, see T4LogLevel Property.●
T4LogFile—specifies the file to which the driver is to write logging information. For information about using this
property, see T4LogFile Property.
●
If the application sets several property values, see Precedence of Property Specifications to determine which setting applies.
Message Format
The format of the trace output is
sequence-number ~ time-stamp ~ thread-id
~ [connection-id] ~ [server-id] ~ [dialogue-id]
~ [class].[method][(parameters)] ~ [text]
sequence-number
A unique sequence number in increasing order.
time-stamp
The time of the message, for example 10/17/2004 12:48:23
thread-id
The thread identifier within the JVM.
connection-id
If applicable, a unique ID for the connection associated with the message.
server-id
If applicable, information about the MXCS server associated with the message. The server-id is of the form:
TCP:node-name.server-name/port-number:NonStopODBC
where
node-name
is the name of the NonStop server node.
server-name
is the Guardian name of the server.
port-number