If you are working with EBCDIC data and your sources and targets have fixed-length records, you should tell Connect ETL that the data is EBCDIC-encoded by selecting “EBCDIC” in the “Treat data as encoded in:” list. (This setting is in the source file dialog.) This will ensure that all comparisons are done correctly and efficiently.
Currently Connect ETL does not support file-level encoding for Micro Focus file formats. Therefore, if one of your sources or targets is Micro Focus format, you should not specify file-level encoding for any of the other sources or targets. Instead, specify encoding at the field level using the record layout. Note that only the lowest-level fields will be treated as EBCDIC in this case. Composite (grouped) fields will not have an encoding).
You will also need to encode any text constants in values you create. The easiest way to do this is using the Encode() function. For example, to create a value containing the string “HELLO” in EBCDIC, you can enter the following into the Expression Builder:
Encode('HELLO', 'EBCDIC')If you need to perform a comparison using a data field that does not have an encoding set (for example a composite field used with a file that does not have file-level encoding), you will need to use hexadecimal values to represent the EBCDIC data. In this case, the string “HELLO” would be represented as:
'\xC8\xC5\xD3\xD3\xD6'