Data Transformation Engine Map Designer Reference Guide

Chapter 16 - Map Audit Auditing Data Content
Map Designer Reference Guide
246
A sample of the burst audit data information is:
<Burst count="1">
<DataLog>
<output card="1">
<object index="1" level="1" size="24" status="V00">Text1 Field</object>
</output>
</DataLog>
</Burst>
Data Content Information in the Audit Log
You can audit input and output data. The data audit settings determine what
information about the data is written to the audit log.
Auditing data keeps track of specified objects in the input(s) and/or output(s) of a
map. The burst audit data information in the audit log can track every occurrence
of a record in a file and record the total count of records.
In the resulting audit log, the <DataLog> section follows the </Burst> tag.
Within <DataLog>, there is an entry for the first input card. Within the input
entry, there is an entry for each occurrence of the object.
Note If item data is specified in an audit setting, and the item is to be interpreted as
binary, the line following the object line has the start tag <Hex> and the data is
presented as pairs of hex digits for each byte.
In the audit log, the <DataLog> section follows the </Burst> tag. Within
<DataLog>, there is an entry for the first input card. Within the input entry,
there is an entry for each occurrence of the object.
Note If item data is specified in an audit setting, and the item is to be interpreted as
binary, the line following the object line has the start tag <Hex> and the data is
presented as pairs of hex digits for each byte.
Auditing Data Content
You can audit input and output data. The data audit settings determine what
information about the data is written to the audit log.
To include data information in the audit log
1 Select the map for which you want to create an audit log.