Data Transformation Engine Map Designer Reference Guide

Chapter 17 - Debugging a Map Unknown Data
Map Designer Reference Guide
265
Unknown Data
When input data is validated, additional data that does not validate as part of the
input may also be found. This data is unknown data.
An example input is composed of Product(s) and Product is not defined with
properties that allow its existence to be predetermined.
The second Product is invalid because the Quantity field is missing. Shown
below is the data:
fork,20
plate,
glass,8
The Quantity
field is missing
When the invalid Product is found, it is not known to exist. Therefore, it is
assumed to be unknown data.
Shown below is a portion of the trace file:
(Level 2: Offset 9, len 5, comp 1 of 2, #1, DI 00000004:)
Data at offset 9 ('plate') was found to be of TYPE
X'0004' (Item Data).
(Level 2: Offset 15, len 0, comp 2 of 2, #1, DI 00000005:)
COMPONENT number 2 of TYPE X'0003' (Product Data)
is required, but does not exist.
(Level 1: Offset 9, len 0, comp 1 of 1, #2, DI 00000004:)
COMPONENT number 1 of TYPE X'0002' (File Data):
occurrence 2 is optional and has no content.
(Level 0: Offset 0, len 7, comp 1 of 0, #1, DI 00000004:)
Data at offset 0 ('fork,20') was found to be of TYPE
X'0002' (File Data ).
INPUT 1 was valid but contained 21 bytes of unknown data at the end.
The entire
File
is
j
ust the first
Product
The
Product
field is missing
The second
Product
is missing
Everything after the first
Product
is unknown data
Note Sometimes a message about unknown data is not significant. You may get a
message about unknown data because there are extra carriage returns or “junk”
data at the end of an input file. You should read the trace file to determine
whether all of the pertinent input data was found.