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.
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.
Overriding a database target
Suppose you want to run the map multitran.hp, overriding some of the settings for the fourth output card, which is a database target.

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:
- 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.
  - Running a map located in a different directory
    From a UNIX™ command line, enter:
  - Creating work files in an alternate directory
    From a Windows™ command line, enter:
  - Executing multiple maps from a single command
    From a Windows™ command line, enter:
  - Overriding a database target
    Suppose you want to run the map multitran.hp, overriding some of the settings for the fourth output card, which is a database target.
  - Overriding the schema location at run time
    When you have a map that is designed to parse input XML data, but want to use a different schema location than what was set up in the Metadata location setting for the root type on the input card in the Map Designer GUI, run the map from the command line and override the map settings.
  - Executing a command file
    As an alternative to typing execution commands on the command line, you can run maps using maps and execution commands in a command file.
  - Using a run function and echoed outputs in memory
    When using the Output Target Override - Echo execution command (-OE) with the X option, the output is stored in memory and is not echoed back to the calling map or application.
  - Audit Log in memory
    Similar to how the data built for an output card can be echoed back to a calling map or application, the audit log, including Data and Execution information, can be placed in memory using the MapAudit execution command (-A) with the M option and echoed back to its calling map or application with the E option
- 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.

Overriding a database target

Suppose you want to run the map multitran.hp, overriding some of the settings for the fourth output card, which is a database target.

Use the following command:


           /install_dir/dtxcmdsv multitran.hp -G -OD4R5:3B "`-DELETE -TRACE ERROR'"

Option

Description

multitran.hp

This specifies the name of the map to be executed, multitran.hp.

-G

All item properties, including size, presentation, and restrictions, are fully validated.

-OD4R5:3B "`...'"

This changes settings for the database target for the data of output card #4 as follows:

R5:3

If the database resource is unavailable, attempt to make the connection five more times at three-second intervals

B

If the map does not complete successfully, roll back any changes made to the database table

"`-DELETE -TRACE ERROR'"

These database-specific adapter commands described in the Resources Adapters documentation indicate that all rows in the target database table should be deleted before processing the output data and a trace file should be generated that only contains error information.