Data Transformation Engine Map Designer Reference Guide

Chapter 17 - Debugging a Map Using the Audit Log as a Debugging Aid
Map Designer Reference Guide
269
Shown below is a portion of the trace file, illustrating how the validation process
determines that the record is a C Record:
(Level 1: Offset 34, len 0, comp 1 of 1, #4, DI 00000001:)
Data at offset 34 ('C*sweater,15\r\nB*...') does not match INITIATOR 'A*'
of TYPE X'0006' (A Record Data ).
(Level 1: Offset 34, len 0, comp 1 of 1, #4, DI 00000001:)
Data at offset 34 ('C*sweater,15\r\nB*...') does not match INITIATOR 'B*'
of TYPE X'0007' (B Record Data).
(Level 1: Offset 36, len 0, comp 1 of 1, #4, DI 00000001 :)
Type X'0008' (C Record Data) is known to exist.
(Level 2: Offset 36, len 7, comp 1 of 2, #1, DI 00000001:)
Data at offset 36 ('sweater') was found to be of TYPE
X'0004' (Item Data).
(Level 2: Offset 44, len 2, comp 2 of 2, #1, DI 00000001:)
Data at offset 44 ('15') was found to be of TYPE
X'0005' (Quantity Data).
(Level 1: Offset 36, len 10, comp 1 of 1, #4, DI 00000001:)
Data at offset 36 ('sweater,15') was found to be of TYPE
X'0008' (C Record Data).
(Level 1: Offset 36, len 10, comp 1 of 1, #4, DI 00000001:)
Data at offset 36 ('sweater,15') was found to be of TYPE
X'0003' (Record Data).
It does not have
the initiator of an
A Record
It does not have
the initiator of an
B Record
C Record
is
known to exist
C Record
i
s found
The object is also
a
Record
Notice the last paragraph in the trace file shown above. After the object is found
as a C Record, it is also found as a Record. Any object that is a partition is also
an object of the partitioned type.
Viewing Results in Hex Mode
Run results can be viewed in hex mode, which displays the offset values of the
data. This may be helpful if the trace file indicates a problem at a particular offset
in the data. To view run results in hex mode, enable the Display In Hex Mode
check box in the Run Results dialog box.
Using the Audit Log as a Debugging Aid
The audit log stores information you request about your data. You can use it for
debugging purposes by having it track invalid data.
Note For a detailed discussion on using the audit log, see Chapter 16 - Map Audit.