Data Transformation Engine What's New Reference Guide

Chapter 2 - Version 6.7.1 Resource Registry
What's New Reference Guide
11
2 represents the two audit codes (13 or 14) for failing minimum or
maximum size requirements (TooLong TooShort).
Audit Log
A new attribute has been added in the Log section of the MapSettings audit to
reflect the SizeValidation attribute.
<Log executionsummary="Always" databurst="Never"
databurst_sizevalidation="TooLongTooShort" executionburst="Never"
mapsettings="Always" datasettings="Always"/>
The options for databurst_sizevalidation are now TooLongTooShort and
WrongSize.
Trace File Modifications
Regardless of the map setting used, this enhancement affects the input trace file.
Instead of a message stating that the data is the wrong size for the type, it will
state that the data failed the minimum or maximum size requirement for the type.
However, there might be individual cases where the wrong size message will be
appropriate, such as where the data for a decimal item is within its minimum and
maximum length, but contains too many or too few decimal places.
About Existing Maps
With the exception of the trace file modification, this enhancement does not
introduce a change in behavior for existing maps. You do not need to recompile
maps that were originally compiled prior to this release unless you desire to use
this new setting to receive the two separate audit codes for too long/too short.
Example Files
The type tree for the Audit Log example (tryaudit.mtt) that is included with the
Integration Broker has been modified to accommodate this enhancement.
Resource Registry
The new enhancements for the Resource Registry include the ability for resource
aliases to be masked in log files and for a Resource Registry-specific trace file to
be created.