To make translation of a document more efficient, Data Interchange Services client uses control strings to drive translation. There are several types of control strings used within Data Interchange Services client. The visible control strings are the map control strings. Instead of using a map directly, the translator component of WebSphere Partner Gateway uses a control string representing the map. Maps are never directly used to translate a document. Map control strings are created by compiling maps. Map control strings are required for all map types: data transformation maps, validation maps, and functional acknowledgment maps.
When you compile a map, control strings are generated for the map and often for the source and target document definitions referenced by the map. The map control strings associated with compiled maps can be listed on the Control Strings list window in the Mapping Functional Area. Control strings associated with document definitions can not be viewed. These are managed with the map control strings. Document definition control strings are exported with the map control strings that need them.
Map control strings should be recompiled any time the corresponding map is changed or any time the related source or target document definition is changed. Changes will not be available to the translator component of WebSphere Partner Gateway until the recompile has been successfully completed and the new control string has been exported to the database accessed by the translator component.