Cross-platform WTX maps

The following general recommendations should be taken into account when developing WTX/FTM maps for cross platform use.

  1. The Data Language property of the Input Card 2 – Source of the InBound should be changed to "Latin1".
    Note: Any functions that reference this card data also have to be changed.
  2. The return type of the submap is schema, so the common map needs to know that the data is UTF-8. This is done by wrapping the RUN statement in CTEXT(…,"UTF-8").
  3. The Data Language property of the Common Maps Output Card 10 – EndMapper must be set to "UTF-8".
  4. When passing data using schema type trees to submaps, use HANDLEIN instead of ECHOIN as ECHOIN will do a conversion to the native code page (for example, EBCDIC on z/OS®).
  5. The Data Language property of the Output Card 10 – SwiftMessage of the OutBound map should be changed to "Latin1".
  6. When using the WTX PUT function with the WIRE keyword on the z/OS platform to map an output to a specific terminal, the conversion of the data to the native code page of the platform (for example, EBCDIC) needs to be overridden. This is because FTM expects the data to be returned as UTF-8. To do this, the PUT WIRE statement uses CTEXT(…,"Native") to convey to the map that the output shouldn't be converted, and should be left in its current code page. For example, UTF-8.
    PUT("WIRE","out10", CTEXT(EndMapperXML,"Native") )
Note: This list should not be considered exhaustive. There may be other cross platform issues in other maps that have not been encountered.