Purpose
Indicate the use of DTL and the corresponding DTL syntax.
Format
/DTL [runtime_variable_setting] [encoding_settings]
where
| runtime_variable_setting | = | RUNTIMEVARIABLES {ON | OFF} |
| encoding_setting | = | ENCODING {LOCALE | UTF-8} |
Location
This option must be the first option in the task definition.
Defaults
The RUNTIMEVARIABLES clause default setting for enabling the inclusion of runtime variables anywhere in subsequent task definitions is set to ON. You need not explicitly set the RUNTIMEVARIABLES clause to ON to set this default behavior.
To disable the inclusion of runtime variables anywhere in subsequent task definitions, set the RUNTIMEVARIABLES clause to OFF.
If the ENCODING clause is not specified, the default depends on whether the DTL file has the UTF-8 BOM. If the file has the UTF-8 BOM, the default is UTF-8. If there is no BOM, the default is LOCALE. For details on encoding, see File Name and Syntax Requirements .
Notes
To intitate task processing, the task execution command option, /RUN, can be used to pass the appropriate task file to the Connect ETL executable. To specify use of DTL syntax for processing, the /DTL option must be listed as the first option in the task file.
Connect ETL enforces that the /DTL option and all subsequent command options conform to DTL syntax. If non-compliant DTL syntax exists in the command options, the Connect ETL task aborts.
Runtime Variables
Runtime variables are specified using environment variables.
By default, the RUNTIMEVARIABLES setting is ON and allows for any part of the task definition to be specified as an environment variable. At runtime, Connect ETL scans the command options for environment variables and replaces them with their defined values.
The Connect ETL task Editor, on the other hand, supports environment variables only in limited places, such as in a table name, database name, file paths, and text contstants, among others.
If your intent is to load a DTL task into the Task Editor at some point, to avoid issues, only use environment variables in places supported by the Task Editor. For a list of places where environment variables are supported in the Task Editor, see Using environment variables in a Connect ETL task or job in the Connect help.