Data Transformation Engine Execution Commands Reference Guide

Chapter 2 - Execution Commands List of Execution Commands

Execution Commands Reference Guide

Option Description

The card (data) settings audit information includes:

♦ the data settings for sources and target cards

The map settings audit information includes:

♦ the map settings

The memory setting can be used only when the map is run by the

RUN() function or an API. If memory is set, audit information is

stored in memory and appended to the last set of data returned

during map execution.

When the map is run by a Command Server or Event Server, this

setting is ignored and the audit log is created in a file in the map

directory, using the <mapname>.log naming convention.

Note If the audit in memory fails or there is insufficient available

memory, a Disk write error or Not enough memory to execute

map message can be returned.

Only use with the memory option (M). This option prefixes the audit

data with a text number indicating the size (in bytes) of the

audited data followed by a space.

This option causes the resulting audit log entry to be returned as

an ASCII number followed by a space, then followed by the

specified number of bytes of data. This helps to distinguish it from

multiple character strings in the returned data when at least one

output and the audit log are echoed.

For example, if used in a RUN() function:

RUN (“mymap.mmc”,”-OE3S -ADEMS”)

If the data resulting from output card #3 was This and That, the

string returned by this RUN() function is:

13 This and That1031 BEGIN RUN Function for Windows….