Data Transformation Engine Design Studio Tutorial

Chapter 15 - Creating a Trace File Scenario
Design Studio Tutorial
260
Copies of the files created during the exercises are provided for all chapters in the
Tutorials\Solutions folder. The structure and use of these files is described in
the Design Studio Tutorial Solutions section on page 18.
Scenario
You want more information on your data validation.
Trace File
When input data is traced, the trace file provides a step-by-step account of the
data objects found, the reason the data is found to be invalid, sizes and counts of
data objects, and the data object position in the data stream. When output data is
traced, the trace file specifies the objects that are built and the output objects that
evaluate to NONE.
A trace file of input messages contains a message for each input data object that
shows:
♦ The level of the object in the card.
♦ The offset of the data object in the data stream.
♦ The length of the data object.
♦ The component number of the data object.
♦ The index of the component.
♦ A portion of the actual data.
♦ The name of the type to which it belongs.
For input data tracing, a message exists in the trace file for each input data object
indicating whether the data object is valid. If the data is invalid, the message
indicates the reason the data is invalid.
The trace file is created as specified after the map is compiled and executed.
The default name of the trace file is the executable map name, plus the file name
extension .mtr. The default location of the trace file is the map execution
directory. A specific name and location of the trace file can be defined in the Map
Settings dialog box.
For example, if your executable map name is RegionReport, the trace file is
RegionReport.mtr.
After you run a map, the trace file can be viewed on the Trace tab in the
organizer window or with any text editor.