Data Transformation Engine Map Designer Reference Guide

Map Designer Reference Guide
255
Chapter 17 - Debugging a Map
This chapter discusses various debugging aids and can assist you in situations
where when running a map, the following types of errors occur regarding input or
output data:
♦ data is invalid
♦ data contains invalid objects
♦ unknown data exists
When you run a map, the input data is validated. Input data validation occurs by
comparing the data to its definition in the type tree. After validating data, the
output card map rules are evaluated and the output objects are built.
If you run a map and invalid or unknown input data is encountered, you can
analyze what happened during the validation process. In addition, you can analyze
the output data.
Debugging Aids
If you run a map and get a run-time error, or you do not get the expected output,
use any or all of the following debugging tools:
♦ Command server window
♦ trace file
♦ audit log
♦ Run Results windows
♦ validation run option settings
Command Server Window
After a map is run, a run-time message appears in the command server window.
This message provides information about the map. For example, the message Map
completed successfully indicates that all inputs are valid. The message One or
more inputs was invalid indicates that an input card object is invalid.
The message One or more inputs was invalid may occur even if you are
absolutely sure that the input data is valid. In that case, there may be an error in
the data definitions in the Type Designer.