Data Transformation Engine What's New Reference Guide

Chapter 3 – Version 6.7 RUN Map Behavior Change
What's New Reference Guide
20
RUN Map Behavior Change
Behavior has changed for files created by RUN maps. If the Scope card setting is
set to Map with the OnFailure setting set to Rollback, the file will not be created
until the top map has completed successfully.
Note that the scenario in which a top map calls multiple RUN maps, where early
RUN maps create files for later RUN maps, will no longer work if the Scope card
setting is set to Map with the OnFailure setting set to Rollback (or in the case of
the Event Server, just Scope > Map).
Prior to this behavior modification (versions 6.5.2 and 5.0.5), files created in RUN
maps (Scope card setting set to Map ) were created when the RUN map finished.
To achieve this earlier behavior, set the Scope card setting to either Card or
Burst.
Backup File Enhancement
This enhancement provides a means whereby unique backup file names can be
generated, or whereby the name of the backup file can participate in wildcard
coordination with the other sources and targets of the map.
Audit Log Enhancements
The following enhancements have been made to the audit logs:
♦ Full audit log support for OS/390 platform: A fully XML-compliant audit log for
the OS/390 platform that contains the same detail as the audit log for the
UNIX and Windows platform is now available. It includes additional OS/390
batch execution map audit and OS/390 CICS audit command sub-options.
♦ Expanded options for creating audit logs: The ability for writing the audit log
only under specific scenarios to facilitate the process of handling audit logs only
when exceptional circumstances occur is now available.
This enhancement provides you with more flexibility in determining the
conditions for creating or appending audit logs.