17.4.3 Information output when trace level is 2

The following is an example of the information output when 2 is selected as the trace level.

▪ Output example (trace level 2)

[Figure]

The following table explains each item of information output at trace level 2.

Table 17‒6: Information output as HADB ODBC driver trace information (trace level 2)
No.	Output item	Description
1	`[Trace Start Time]`	The date and time at which output of the HADB ODBC driver trace information started. If HADB could not acquire the time, 0 is output in all date and time fields.
2	`[Process ID]`	The process ID
3	`[Module Name]`	The name of the module that uses the HADB ODBC driver. If HADB cannot identify the module name, `unknown` is output.
4	`[Platform]`	The platform on which the HADB ODBC driver is operating
5	`[ODBC environment variables]`	The values of the environment variables used by the HADB ODBC driver. The values output here are not necessarily the values specified in the environment variables. They are the values actually being used by the HADB ODBC driver, which might be the default values or a value explicitly specified in ODBC Data Source Administrator. `ADBCLTLANG` The character encoding used by the HADB client `ADBODBTRC` Whether HADB ODBC driver trace information is to be output. `ADBODBTRCSIZE` The maximum size of each HADB ODBC driver trace file `ADBODBTRCPATH` The absolute path of the folder in which HADB ODBC driver trace files are stored `ADBODBTRCLV` The specification of the trace level `ADBODBAPMODE` The application mode of the HADB ODBC driver For details about the preceding environment variables, see 4.3.1 HADB client for Windows.
6	`ACCESS`	The access type `[E]`: Called by the function. `[R]`: Returned from the function.
7	`FUNCTION`	The name of the ODBC function
8	`HANDLE`	The value of the handle passed as an argument to the ODBC function. In 32-bit environments, the handle will be output a string of eight characters prefixed with the two characters 0x. In 64-bit environments, the handle is a 16-character hexadecimal value.
9	`START-TIME`	The time at which the ODBC function started executing. If HADB could not acquire the time, 0 is output in all date and time fields.
10	`END-TIME`	The time at which the ODBC function finished executing. If HADB could not acquire the time, 0 is output in all date and time fields. When the access type is `[E]`, `*` is output.
11	`RETURN`	The symbol name that represents the value of the `SQLRETURN` data type that is the execution result of the ODBC function. If the value is unknown, `unknown` is output instead of the symbol name. When the access type is `[E]`, `*` is output.
12	`SQLSTATE`	The value of `SQLSTATE`. This information is only output if executing the ODBC function results in output of a `SQLSTATE` value. When the access type is `[E]`, `*` is output.
13	`CON_ID`	The connection number. This is the same as the connection number output in SQL trace information. If the ODBC function had not yet connected to the HADB server, `*` is output.
14	`CON_NUM`	The connection sequence number. This is the same as the connection sequence number output in SQL trace information. If the ODBC function had not yet connected to the HADB server, `*` is output.
15	`[Input]`	The input parameters. Input parameters are output in the following format: `variable-name (data-type-name)` `=` `value (symbol-name-or-referenced-data)` Parenthesized information is omitted in some cases. If the value is unknown, `unknown` is output instead of the symbol name.
16	`[Output]`	The output parameters. Output parameters are output in the following format: `variable-name (data-type-name)` `=` `value (symbol-name-or-referenced-data)` Parenthesized information is omitted in some cases. If the value is unknown, `unknown` is output instead of the symbol name. This information is not output if the ODBC function does not have output parameters.
17	Connection user name and password	The user name and password used to establish the connection. A single asterisk `*` is output in place of the password.
18	`Connect Info`	The information output when the connection with the HADB server was established
19	`[DataSourceName]`	The name of the data source to which the HADB ODBC is connected. If the driver is not using a data source or is using a file DSN, `*` is output.
20	`[Client Definition File Path]`	The path of the client definition file
21	`[Hitachi Advanced Data Binder ODBC Driver Version]`	The version of the HADB ODBC driver.
22	`[ProcessID]`	The process ID of the HADB client
23	`[SYSTEM]`	Information specific to HADB. For details, see Table 17‒7: Information output in [SYSTEM]. The information output for SYSTEM differs between ODBC functions.
24	`<Message>`	A message that provides diagnostic information. A message is output when the execution result of the ODBC function is one of the following: `SQL_ERROR` `SQL_SUCCESS_WITH_INFO` `SQL_NEED_DATA` (when the function is `SQLBrowseConnect`)

The following table lists the information output for [SYSTEM] in the preceding table.

Table 17‒7: Information output in [SYSTEM]
No.	Type	ODBC function name	Information output in `[SYSTEM]`
1	Connections with data sources	`SQLAllocHandle`	None
2		`SQLConnect(W)`
3		`SQLDriverConnect(W)`
4		`SQLBrowseConnect(W)`
5	Acquisition of driver and data source information	`SQLDataSources(W)`	None
6		`SQLDrivers(W)`
7		`SQLGetInfo(W)`
8		`SQLGetFunctions`
9		`SQLGetTypeInfo(W)`
10	Setting and acquiring driver options	`SQLSetConnectAttr(W)`	None
11		`SQLGetConnectAttr(W)`
12		`SQLSetEnvAttr`
13		`SQLGetEnvAttr`
14		`SQLSetStmtAttr(W)`
15		`SQLGetStmtAttr(W)`
16	Setting descriptor values	`SQLGetDescField(W)`	None
17		`SQLGetDescRec(W)`
18		`SQLSetDescField(W)`
19		`SQLSetDescRec`
20		`SQLCopyDesc`
21	Creating SQL requests	`SQLPrepare(W)`	`tran_id`: Transaction ID `stmt_hdl`: Statement handle ID `sql_serial_num`: SQL statement sequence number
22		`SQLBindParameter`	None
23		`SQLGetCursorName(W)`
24		`SQLSetCursorName(W)`
25		`SQLDescribeParam`
26		`SQLNumParams`
27	SQL execution	`SQLExecute`	`tran_id`: Transaction ID `stmt_hdl`: Statement handle ID `sql_serial_num`: SQL statement sequence number
28		`SQLExecDirect(W)`
29		`SQLNativeSql(W)`	None
30		`SQLParamData`
31		`SQLPutData`
32	Acquiring execution results and execution result information	`SQLRowCount`	None
33		`SQLNumResultCols`
34		`SQLDescribeCol(W)`
35		`SQLColAttribute(W)`
36		`SQLBindCol`
37		`SQLFetch`
38		`SQLFetchScroll`
39		`SQLGetData`
40		`SQLSetPos`
41		`SQLBulkOperations`
42		`SQLMoreResults`
43		`SQLGetDiagField(W)`
44		`SQLGetDiagRec(W)`
45	Acquiring system information for data sources	`SQLColumnPrivileges(W)`	None
46		`SQLColumns(W)`
47		`SQLForeignKeys(W)`
48		`SQLPrimaryKeys(W)`
49		`SQLProcedureColumns(W)`
50		`SQLProcedures(W)`
51		`SQLSpecialColumns(W)`
52		`SQLStatistics(W)`
53		`SQLTablePrivileges(W)`
54		`SQLTables(W)`
55	Terminating SQL execution	`SQLFreeStmt`	When `Option=SQL_CLOSE`, the following information is output: `tran_id`: Transaction ID `stmt_hdl`: Statement handle ID `sql_serial_num`: SQL statement sequence number
56		`SQLCloseCursor`	`tran_id`: Transaction ID `stmt_hdl`: Statement handle ID `sql_serial_num`: SQL statement sequence number
57		`SQLCancel`	None
58		`SQLEndTran`	`tran_id`: Transaction ID
59	Disconnecting from data sources	`SQLDisconnect`	None
60	Disconnecting from data sources	`SQLFreeHandle`	None

Note:: In some circumstances, such as when the transaction has been settled, HADB might be unable to acquire tran_id, stmt_htdl, and sql_serial_num. In this case, * is output for each value.

To Page Top