Data Transformation Engine Map Designer Reference Guide

Chapter 16 - Map Audit Audit Log Contents
Map Designer Reference Guide
243
Some information is optional, and does not always appear in the
ExecutionSummary element of the audit log. For example, information about
objects found and built is provided only when using a command engine.
WorkArea data is provided only when a work area is used during map processing.
Elapsed Execution Time in the Audit Log
The execution audit log records the elapsed time. The elapsed time format is
presented differently on Windows platforms than on non-Windows platforms.
♦ On Windows platforms, the elapsed time of map execution is described to four
decimal places.
♦ On non-Windows platforms, the elapsed time of map execution is presented in
whole seconds only (rounded).
Note When using the audit_2.mtt type tree from the examples (install_dir/examples)
to read map audit logs, modify the type tree appropriately for the execution
platform.
Source Data Report By Card
In the audit log, the source data report by card provides information on:
♦ Value of the adapter Source card setting
♦ Source data byte count
♦ Adapter return code and message
♦ Adapter command line or file path
♦ Data source time stamp
Target Data Report by Card
In the audit log, the target data report by card provides information on:
♦ Value of the adapter Target card setting
♦ Target data byte count
♦ Adapter return code and message
♦ Adapter command line or file path
♦ Data target time stamp