The public log for a Teradata PT job is automatically generated and filed by the job name. The information is updated as the job runs and is presented in the sequence it is encountered.
Public Log Contents
The public log contains the following information about a job:
- Teradata PT Version Number
- An overview of the activities of each operator including stages of operator task execution, errors encountered, warnings, and a summary of data sent and received.
- Number Of Sessions
- Blocksize Used
- Number Of Blocks Created
- Task Status Codes
- Checkpoints Taken
- Restarts Attempted
- Job Elapsed Time
- Job CPU Time
Multiple operators can run within a single job. They all write asynchronously to the same public log. Information in the public log is not sorted, but is written to the log as it is received.
Accessing a Public Log by Job Name
To access the public log for a particular Teradata PT job, enter the following tlogview command:
tlogview -j <jobname>-<job sequence number>
- <jobname> is the name of a previously launched job, as specified in the jobname parameter of the tbuild command.
- <job sequence number> is a number generated by the Teradata PT that enumerates the Teradata PT jobs submitted under the current userid since its installation, and which appears in a console message as soon as the job starts executing.
Accessing a Public Log with No Associated Job Name
If no job name is specified in the tbuild command, Teradata PT automatically names the public log file using the logged-on user ID, a hyphen, and the <job sequence number>, resulting in public log file names of <userid>-1.out, <userid>-2.out, and so on.
To locate a public log with the default assigned name, execute the following command (a UNIX command shown):
tlogview -l TPT_install_directory/logs/<userid>-<job sequence number>.out
- <userid> is the username employed to log on the job.
- <job sequence number>is a number generated by the Teradata PT that enumerates the Teradata PT jobs submitted under the current userid since its installation, and which appears in a console message as soon as the job starts executing.
The example above is for logs on a UNIX system. Public logs are accessible from the following directories, depending on operating system:
On z/OS platforms you must run a batch job to print out the public log. For information, see “JCL Examples” in Teradata Parallel Transporter Reference (B035-2436).