Encode syntax requirements - Connect_ETL - 9.13

DTL Encoding in UTF-8

To specify that a DTL file is encoded in UTF-8, do either of the following:

• Save the file in UTF-8 with the BOM
• Specify UTF-8 encoding as an argument to the /DTL option:

  /DTL [ RUNTIMEVARIABLES ON|OFF ] [ ENCODING LOCALE|UTF-8]

  Note: LOCALE refers to the locale of the machine where the job/task will run.

When a DTL file is encoded in UTF-8:

• Connect ETL translates all quoted text, that is single-/double-quoted string constants, identifiers double-quoted with a prefix of I, and double-quoted pathnames, from UTF-8 to locale before processing.
• String constants that are Unicode literals, that is, those that should not be translated to locale, must be prefixed with U.

For example, /VALUE value1 U'çççç' means process 'çççç' as a UTF-8 string without translating to locale.

DTL Encoding in LOCALE

In DTL, locale indicates the locale of the machine where the job/task is run. In order for a job/task to run successfully, the locale of the machine where the job/task is run must be the same as the locale of the machine where the job/task was created. In scenarios where design-time and run-time machines have different locales, save the job/task in UTF-8 encoding.

Quoted text is processed without being translated. As mixed encoding is not supported, an error message is generated when a locale DTL file contains string constants prefixed with U.

DTL File Encodings

Consider the following table, which illustrates how Connect ETL treats DTL file encodings: