16.20 - Command-Line Handling of String Delimiters in Script Parsing - Parallel Transporter

Teradata® Parallel Transporter User Guide

Parallel Transporter
Release Number
August 2020
English (United States)
Last Update

A few simple syntax rules govern the tbuild command, and the other Teradata PT commands, at the command prompt on the various supported platforms.

The following examples suggest that single quotes should be avoided as string delimiters for command-line arguments on all platforms.

On All Platforms

  • Double-quote characters ( " ) are interpreted as string delimiters, and are stripped from the character strings they enclose.
  • A double-quote character as a data character in a string must be escaped with the backslash character ( \ ). For example:
    tlogview -j DTAC_FLD1@offshore36-746 -w "TASKNAME=\"SELECT_20001\""

On Windows Systems

On UNIX systems, single quotes (') are stripped away so that quotes are not part of the string. But on Windows systems, the quote becomes part of the string. This means that if you run something like this at the Windows command prompt:

C:\>tlogview -l 'C:\Program Files\Teradata\client\<version>\Teradata 
Parallel Transporter\logs\testjob.out'

the filename is read as 'C:\Program.......testjob.out', including the quotes, which is not the right file name.

On UNIX Systems

  • Single-quote characters are also recognized as string delimiters and are stripped from the character strings they enclose.
  • A single-quote character can be a data character only when it occurs in a string delimited by double-quote characters. For example, in the command:
    tbuild  -f  test_job.twb  -u  "verb=\"Couldn't\""

    the argument of the -u option passed to the tbuild program is the string verb= “Couldn’t”.

On z/OS Batch Systems

  • Command line parameters are entered with the PARM field of the EXEC JCL statement for z/OS batch jobs.
  • Single-quote characters are recognized as the PARM field delimiters and are stripped from the character strings they enclose.