Data Transformation Engine Command Server Reference Guide

Chapter 1 - Using a Command Server Executing a Map
Command Server Reference Guide
8
Note After transferring a platform-specific built map, it is strongly recommended that
you rename the compiled map by using the .mmc file extension. Renaming it is
not necessary; however, it is helpful because an .mmc extension allows the file
name to be identified in mapping functions and executed without specifying the
extension.
Executing a Map
After a map has been built for a specific execution platform and transferred, the
map can be executed using a Command Server.
Using Execution Commands
Using the execution commands and options, you have precise control over how a
map executes. For example, you can override sources and targets specified in the
map, create trace and audit log files, and control a variety of characteristics of the
run-time environment.
Some execution commands are not available on all platforms. For information
about execution commands and their syntax, see the Execution Commands
Reference Guide.
Input Data Validation
When a map begins execution, the input data must first be validated to ensure
that the data for each input conforms to the definition of the corresponding input
card. If it does conform, the data is valid. If the data does not conform, it is
invalid. If data is determined to be invalid, a run-time return code and
corresponding message is issued.
If invalid data is encountered, you may still want the map to continue processing
or you may even want to map the invalid data. This can be accomplished during
map development by using the Restart attribute when defining the input data and
using the
REJECT function when mapping the output data. In addition, functions
are available to test for the presence of errors. For information about using the
Restart attribute, see the Type Designer Reference Guide. For information about
using the error-related functions, see the Functions and Expressions Reference
Guide.
The validation process assumes that source data is a data stream. To find data
objects in the input stream, type tree definitions are used including information
about syntax items, data patterns, restrictions, component rules, and size. To
process your input, the data must be able to be accessed at a designated position,
for a specified length.