Generating the Teradata PT API Operator Log|TD_CHARSET - Generating the Teradata PT API Operator Log - Parallel Transporter

TD_TRACE_LEVEL1 / TD_TRACE_LEVEL2

To generate the Teradata PT API operator log, you must set the following two environment variables:

• TD_TRACE_LEVEL1
• TD_TRACE_LEVEL2

If TD_TRACE_LEVEL1 or TD_TRACE_LEVEL2 is not set, the Teradata PT API operator log is not generated.

The possible values for TD_TRACE_LEVEL1 and TD_TRACE_LEVEL2 are listed in the schema.h file.

The best value for:

• TD_TRACE_LEVEL1 is TD_OPER_ALL
• TD_TRACE_LEVEL2 is TD_GENERAL.

These values generate a complete Teradata PT API operator log.

TD_TRACE_OUTPUT

Setting the following environment variable TD_TRACE_OUTPUT is optional.

• If you are setting TD_TRACE_OUTPUT, you should set it to a file in which the Teradata PT API operator log is generated.
• If you do not set TD_TRACE_OUTPUT, Teradata PT API sets TD_TRACE_OUTPUT to a value with the operator name and timestamp.

TD_TRACE_LOGSQL

Setting the following environment variable TD_LOGSQL is optional.

If this variable is not set, the variable takes the default value, which is No.

Valid values:

• Yes ('Y') = Output the full Teradata SQL in the trace output file when the driver's trace is enabled. The maximum length of the Teradata SQL is 1 megabyte.
• No ('N') = Do not output the Teradata SQL in the trace output file (default).