16.10 - Options for Specifying UTF-8 and UTF-16 in a Job Script - Parallel Transporter

Teradata Parallel Transporter Reference

Product
Parallel Transporter
Release Number
16.10
Published
July 2017
Content Type
Programming Reference
Publication ID
B035-2436-077K
Language
English (United States)

In most cases, all the elements of a job must use a common character set:

  • Data
  • Session character set, as specified in the job script
  • Character set used to encode the job script

However, because of the unique properties of the Unicode character sets supported by Teradata PT on network-attached platforms (UTF-8 and UTF-16), it is possible for the session character set and the job script encoding to use either the same or different Unicode character sets.

Specify the correct Unicode character set in a job script according to the following scenarios:

Specifying Unicode character sets in a Teradata PT Job Script 
Job Script Encoding Session Character Set Character Set Specification
UTF8 UTF8 Specify the character set in the job script as follows:USING CHARACTER SET UTF8 DEFINE JOB…
UTF8 UF16 Specify the character set in the job script as follows:USING CHARACTER SET UTF16 DEFINE JOB…
UTF16 UTF8 Do both of the following:
  • Specify the character set in the job script as follows:USING CHARACTER SET UTF8 DEFINE JOB…
  • Specify the character set on the command line as follows:tbuild -e UTF16
UTF16 UTF16 Do both of the following:
  • Specify the character set in the job script as follows:USING CHARACTER SET UTF16 DEFINE JOB…
  • Specify the character set on the command line as follows:tbuild -e UTF16
Only network-attached clients running Teradata PT support the use of UTF-8 and UTF-16 character sets in job scripts. Mainframe-attached clients running Teradata PT do not support these character sets.