As described above, the USING CHARACTER SET <characterSet> statement in the Teradata PT job script is used to define the session character set. The session character set must match the data and it must match the encoding of the job script.
USING CHARACTER SET UTF8 or
UTF16 specifier is required in the script for the ADJUST UNICODE specifier to
operate correctly in the DEFINE SCHEMA section, if it is absent, the ADJUST SCHEMA
keyword will be ignored. For details, see DEFINE SCHEMA.
When submitting a job script that is encoded in UTF-16, however, you must also specify the -e command line option for the tbuild command.
tbuild -f <filename> [-v jobVariableFile] -e UTF16
-e UTF16 indicates to Teradata PT that the job script is encoded in UTF-16. The file endianness is determined by the Byte Order Mark (BOM) at the beginning of the file.
The following -e options support the different encoding schemes:
- UTF-16 / UTF16 and any upper/lower case variations with or without a hyphen. For UTF-16 scripts: if the script is not UTF-16, error is reported. If the script endianness differs from the platform encoding, the script is converted to the platform endianness before execution.
- UTF-16LE / UTF16LE and any upper/lower case variations with or without a hyphen. For UTF-16 little endian scripts: the script is not little endian, an error is reported. If the platform is big endian, the script is converted to big endian before execution.
- UTF-16BE / UTF16BE and any upper/lower case variations with or without a hyphen. For UTF-16 big endian scripts: if the script is not big endian, an error is reported. If the platform is little endian, the script is converted to little endian before execution.
- UTF-8 / UTF8 and any upper/lower case variations with or without a hyphen. For UTF-8 scripts: if the script is not UTF-8, error is reported.
The job variable and include files in either big endian or little endian format can be executed on either kind of platform.