Data Transformation Engine Map Designer Reference Guide

Chapter 16 - Map Audit Audit Log Contents

Map Designer Reference Guide

245

BurstAudit Execution in the Audit Log

The MapAudit > Switch = On and the BurstAudit > Execution = On map

settings produce an audit log with burst execution information. The burst element

provides information on the performance of the burst.

♦ If all input cards have the FetchAs mode of Integral, there is one burst

element in the audit log.

♦ If any input card has the FetchAs mode of Burst, there is one element for

each burst.

The execution log contains the return code of the burst, the amount of time it took

to process the burst (in seconds), and a status of each input and output. The input

and output status include the card number, the bytes processed, the adapter

return code, and the content return code.

For example, if a burst fails because an adapter could not connect, the audit log

defines which adapter failed. If an input is invalid, the content return code

specifies which input is invalid. If an output rule fails, the content return code tells

you which output failed.

A sample of the burst audit execution information in the audit log is:

</ExecutionLog>

</Burst>

BurstAudit Data in the Audit Log

The MapAudit > Switch = On and the BurstAudit > Data = On map settings

produce an audit log with burst audit data information. The burst audit data

information includes a burst count, the card number, the object index, the audit

log status code, the object level, the size of the object, and the object name.