The coding, i.e. the system-internal representation of individual characters, letters and digits, depends on the operating system. The data must then be converted because
Internally, Unix and Windows computers use an ASCII-based code (American Standard Code for Information Interchange). For Unix systems this is an ISO-8859-x code that is described in ISO standard 8859. For Windows systems, this is a code defined by Microsoft such as, for example, the CP1252 character set with Euro symbol for western Europe.
BS2000 systems and z/OS computers, on the other hand, normally use an EBCDIC (Extended Binary-Coded Decimal Interchange Code).
Data conversion between openFT partners always applies to the characters with which parameter values (e.g. file names, user IDs, follow-up processing strings, etc.) are transferred.
The conversion of file contents, by contrast, is only relevant for files to be transferred in text format; no data conversion is performed by openFT when transferring files in other formats (binary, transparent, etc.).
Please make sure that the openFT partner codes use the same character repertoire. If this is not the case, some of the characters in the text file (e.g. umlauts) may not be represented correctly. If you transfer files with openFT partners as of V10, you can assign the "Coded Character Sets" that are to be used for local and remote data conversion in the request. It is also possible to transfer Unicode files with these partner systems, see section“Transferring 7-bit, 8-bit and Unicode files”.