Product specifications

The traces are logged into a file whose default name is TraceLog_<pid>_<timestamp>_trace.log.
If you want to set another name to the log file, update the BO_TRACE_PROCESS environment variable
with the new name.
9.9.2 To activate traces in server mode
You enable traces for jobs and drivers from the CMC. This allows you to let the server run while enabling
traces.
1.
Start the CMC.
2.
Go to the Properties page of either ConnectionServer server (for Native Connectivity Service) or
Adaptive Processing Server (for Adaptive Connectivity Service).
3.
Under "Low Level Tracing" section, check:
• Enable Job Tracing to enable job traces
• Enable Middleware Tracing to enable middleware traces
Note:
The TraceLog level must be set to High under "TraceLog Service" section.
Remember:
The Enable Middleware Tracing setting allows you to trace all middleware. If you want to trace
only specific middleware, you then need to configure the cs.cfg file and to restart the server.
9.9.3 Reading traces
ENTER traces identify the middleware API call, while EXIT traces identify the returned call. Each function
has its own trace. Traces help you find the following:
• Call expections, if |E| is displayed
• API errors, if the return code -1 is displayed
• An error message if the middleware API fails
• No returned call from a middleware API, if there is no EXIT after ENTER
Example:
The following is an excerpt of a BOE trace example:
2006/11/14 10:49:49.600|<<|||5784|5852|||||||||||||||||unknown|unknown|JobId:0| ENTER SQLAllocHandle
SQLSMALLINT 1
SQLHANDLE 0x00000000
SQLHANDLE * 0x0012F360
2006/11/14 10:49:49.600|<<|||5784|5852|||||||||||||||||unknown|unknown|JobId:0| EXIT SQLAllocHandle with
return code 0 (SQL_SUCCESS)
SQLSMALLINT 1
SQLHANDLE 0x00000000
SQLHANDLE * 0x0012F360
2012-03-15106
Configuring data access global parameters