Data Transformation Engine Execution Commands Reference Guide

Chapter 1 - Executing Maps Using Command Server Commands

Execution Commands Reference Guide

Command Files

You can create command files that contain listings of maps to execute with

execution commands that specify how you want each map to run. A command file

is a text file that can contain multiple maps to run, as well as multiple execution

commands and options for each map; however, a command file cannot run

another command file.

Using Command Server Commands

When you run a map, you can:

♦ Override sources and targets for the cards used in the map

♦ Create trace and audit log files

♦ Control a variety of characteristics of the run-time environment

The execution commands entered when you run a map do not permanently affect

the compiled map file.

The command options that you specify override the settings compiled into the

map file. If you do not use a specific execution command, the corresponding map

and card settings compile into the map.

General Rules for Execution Commands

The general rules that apply when specifying execution commands are:

♦ Each execution command must begin with a hyphen.

♦ At least one space is required between commands (for example, -T -V).

♦ There are no spaces within an option except for the commands that allow you

to override sources and targets (for example,

-I and -O), which require a

space before the source or target name.

♦ If a source or target name contains a space, enclose the entire name in single

quotes.

♦ Execution commands and options are not case-sensitive.

♦ If spaces or single quotes can occur in echoed data specified using the -IE

execution command, the size option should be used (-IExS).

♦ Multiple options may be specified for a single map.

♦ Command files can contain multiple lines. Line breaks can be used to replace of

the required space that must exist between commands. The line breaks are

converted to spaces before to processing.