Home
Execution commands
This documentation includes information about the various ways to use execution commands and their options when executing maps. Execution commands are used to specify how to execute a map.
Using Command Server commands
When you run a map, you can:
General rules for execution commands

Execution commands
This documentation includes information about the various ways to use execution commands and their options when executing maps. Execution commands are used to specify how to execute a map.
- Command Server overview
  Use execution commands to override the map settings or card settings in a compiled map when a map is run using one of the following methods:
- Using Command Server commands
  When you run a map, you can:
  - General rules for execution commands
  - From a command line
    You can execute a particular map or a command file containing a list of maps to execute from the command line of the system hosting your Command Server.
  - From the Platform API
    To run the server using a Platform API, as part of an argument to the RunMap() function, specify:
  - From a RUN() function in a map rule
    To execute a map from a map rule, use the RUN() function as follows:
- List of execution commands
  This documentation contains information about the execution commands and associated options, including the syntax of each command and its particular usage.
- Examples
  This documentation presents a variety of examples involving the execution of maps using various execution commands in a RUN() function and from the command line in UNIX™ and Windows™ environments.
- INI commands for debugging maps
  This documentation presents the dtx.ini (INI) file commands you can use for the debugging of adapter connections for maps run using non event-driven execution methods.

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 can 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.