Specifies the tracing level for the required infrastructure for sending data to Teradata and using the TPT API with Fastload, MultiLoad, or Multi-Statement insert.
| Valid in: | DATA and PROC steps (when accessing DBMS data using SAS/ACCESS software) |
|---|---|
| Category: | Bulk Loading |
| Default: | 1 |
| Restriction: | This option is valid only when using the TPT API. |
| Requirement: | To use this option, you must first specify TPT=YES. |
| Data source: | Teradata |
| See: | Maximizing Teradata Load Performance, Using the TPT API, BULKLOAD= LIBNAME option, BULKLOAD= data set option, MULTILOAD= data set option, MULTISTMT= data set option, TPT= LIBNAME option, TPT= data set option, TPT_TRACE_LEVEL= data set option, TPT_TRACE_OUTPUT= data set option |
Table of Contents
specifies the needed infrastructure tracing level (10 to 18) when loading data to Teradata.
|
Tracing Level |
Description |
|---|---|
|
10 |
no tracing |
|
11 |
operator-level general trace |
|
12 |
operator-level command-line interface (CLI) trace |
|
13 |
operator-level notify method trace |
|
14 |
operator-level common library trace |
|
15 |
all operator-level traces |
|
16 |
Telnet API (TELAPI) layer general trace |
|
17 |
PutRow or GetRow trace |
|
18 |
operator log message information |
You can perform debugging by writing diagnostic messages to an external log file when loading data to Teradata using the TPT API. If you do not specify a name in PT_TRACE_OUTPUT= for the log file, a default name is generated using the current timestamp. See your Teradata documentation for details.