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

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
The name of the NonStop server node.
server-name
The Guardian name of the server.
port-number
The port to which the server is connected.
For example:
TCP:\banshee-tcp.$Z0133/46003:NonStopODBC
dialogue-id
If applicable, the dialogue-id used for the MXCS connection.
class
If applicable, the name of the class that issued the logging request.
method
If applicable, the name of the method that issued the logging request.
parameters
An optional set of parameters associated with the method.
text
Optional textual information for the message.
NOTE: The tilde (~) character separates message parts. This separator allows you to format the
message using tools, such as Excel, Word, UNIX sort, and so forth. For example, you can format
and sort messages based on sequence number or thread ID. You can edit the log file and change
the separator (the tilde) to any character you want. When possible, numbers (such as thread-id
and sequence-number) are pre-pended with zeros (0) to allow for readable formatting.
Examples of Logging Output
• Output where T4LogLevel is set to SEVERE
0000001 ~ 10/22/2004 10:22:19 ~ 001234 ~ 0049934 ~ ~ ~
~ SQLException Operation cancelled.
SQLSTATE = S1008
SQLCODE = 01118
• Output where T4LogLevel is set to FINER
0000006 ~ 10/22/2004 10:34:45 ~ 001234 ~ 0049934 ~ FetchRowSetMessage ~ marshal
~ Entering FetchRowSetMessage.marshal( en_US
, 48345
, STMT_MX_8843
, 5
, 4192,
, 0
, 0 )
The Type 4 Driver Logging Facility 83