Data Transformation Engine Map Designer Reference Guide

Chapter 17 - Debugging a Map Trace File
Map Designer Reference Guide
261
Invalid Data
When a data object does not match the definition of the type to which it
presumably belongs, it could be invalid.
Following are possible reasons for an invalid data object:
♦ Item value is not in restriction list
♦ Item failed the presentation test
♦ Item is the wrong size
♦ Data object has the wrong delimiter
♦ Data object has the wrong terminator
♦ Data object failed the component rule
♦ Group is missing a required component
♦ Group contains one or more invalid component(s)
Invalid Card Objects
If an entire card object is invalid, a run-time message appears in the command
server window, indicating that the data is invalid. For example, if an input source
is a file and the file is invalid, when the map is run, the message One or more
inputs was invalid may appear.
If you trace the card containing the invalid object, a message in the trace file
indicates that the card data object was invalid. If the data object of input card 1 is
File and is invalid, the trace file would indicate this with the following message:
Input 1 exists, but it is invalid.
Prior to the message that the entire card object is invalid, there is an explanation
of why it is invalid. For example, it might be that a required component of the
card object is in error. The message about the invalid component will contain a
negative word such as - not, failed, wrong, or invalid.