Rational Developer for System z

Automatic group mapping

This topic describes the automatic group mapping feature of the mapping editor.

Automatic group mapping is a feature of the mapping editor that automatically creates mappings between the members of a user-defined XML complex type and the members of a compatible high-level-language structure (COBOL or PL/I).

This feature is available with both request mapping files and with response mapping files. To create an automatic group mapping:
  1. Select the XML complex type on one side of the mapping editor.
  2. Select a compatible high-level-language element (COBOL or PL/I) on the other side of the mapping editor.
  3. Click the Map the matching elements icon on the mapping editor toolbar.
The mapping editor creates a mapping (that is, a Move transform) between each member of the XML complex type and the corresponding member of the compatible high-level-language structure.
Note: This feature is not available if the high-level-language data structure contains any element that already has a mapping.

COBOL data structure

With COBOL data, the data structure must be a COBOL group that is structurally compatible with the XML complex type. The COBOL group is considered to be structurally compatible if the following conditions are met:
  1. The XML instance document and the COBOL language structure it is being mapped to meet the following requirements:
    1. A composed element is an element containing other elements. Each composed element of the XML instance document starting from the root has one and only one corresponding COBOL group item whose nesting depth is identical to the nesting depth of its XML equivalent.
    2. A non-composed element is an element that does not contain other elements. Each non-composed element in the XML instance document starting from the top has one and only one corresponding COBOL elementary item whose nesting depth is identical to the nesting level of its XML equivalent and whose memory address at run time can be uniquely identified.
    3. For the request mapping, the innermost complex type contains at least one simple type compatible in type with that of its COBOL mapped item.
    4. For the response mapping, every XML complex type must contain the same number of simple types compatible with that of their COBOL mapped items.
  2. The mapped COBOL group does not contain subordinate redefining items. (The mapped group itself can be a redefining item)
  3. The mapped COBOL group does not contain OCCURS DEPENDING ON constructs.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)