Data Transformation Engine Map Designer Reference Guide

Chapter 17 - Debugging a Map Negative Messages Not Fatal
Map Designer Reference Guide
266
Negative Messages Not Fatal
Sometimes validation of a given data object interprets the given data object as
belonging to a type to which it does not really belong. In this situation, the data
object will fail to belong to that type - but that is because the data does not
belong.
In the following two situations, you may see messages that a data object fails to
belong to a certain type because it is not really data of that type:
♦ When an optional occurrence of a component that does not exist in the data is
sought during validation
♦ When an object of a partitioned type is sought during validation
The following sections provide additional information and examples of these two
cases.
Example of Optional Occurrences
If an occurrence of a component is optional, there may be more than one
possibility for a given data object. For example, suppose a type has the following
components:
A (1:3)
B
After A is found, the next object in the data stream can either be A or B. Suppose
it is B. Therefore, the object fails to be A. A message in the trace file indicates
that the object does not match the definition of A in some way. After the
validation process has determined that the object is not A, validation occurs to
determine whether it is B. Then the object is validated as B.
It is acceptable if an optional occurrence of a component does not exist in the
data; it is optional. However, if a required occurrence of a component does not
exist, the data object containing that component is invalid.