17.10 - TPT Log Support - Access Module

Teradata® Tools and Utilities Access Module Reference

Product
Access Module
Release Number
17.10
Published
October 2021
Language
English (United States)
Last Update
2021-11-02
dita:mapPath
uur1608578381725.ditamap
dita:ditavalPath
obe1474387269547.ditaval

The Teradata Access Module for GCS supports the use of TPT logs. The console output contains the necessary information to show job progress. The detailed information is written to the TPT logs.

Writing the access module messages to the TPT logs allows the output to be saved (prior to this enhancement, all messages went to the console and when the console is no longer available, the history of the access module job is lost).

When LoggingFlags is enabled in the initialization string, the debug/trace information will be written to the logs and not to the console.

Some trace messages will be written to the console if the processing of those messages takes place prior to the logs being opened (especially the parsing of the initialization string).

To review/output the information from the TPT logs, use the tlogview command (redirecting the output to an output file as there will be a considerable amount of information).

For example:

tlogview -j <job-id> -f "*" -g > output-file

Where:

<job-id> is the id of the TPT job. output-file is the name of the file to contain the log output.

Alternately, you can run the tdlog command:

tdlog <job-id> > output-file

For more information, refer to TPT Reference Manual (B035-2436).

The name of the private log in the TPT log is GCSAXSMOD-n, where 'n' is the instance number.