On Unix and Windows systems, openFT supports different character coding for the specification of
remote file names and directory names,
pre, post and follow-up processing,
remote commands
A distinction is made between the transparent mode and the character mode for these parameters
Transparent mode
file names, etc. are seen in a fixed binary code, independent of local character code settings. Code transformation merely takes place between EBCDIC DF.04-1 (BS2000), IBM1047 (z/OS) and ISO8859-1 (Unix, Windows). If the systems involved use different code variants to present their file names, the characters may then change. Transparent mode is compatible with the previous versions of openFT.
Note on Windows systems
In Windows there is a certain dependence on the locally set ANSI code for remote file names and command strings in remote follow-up processing in transparent mode, because file names and commands were seen in local ANSI code in earlier openFT versions at the Windows system interfaces. Regardless of the selected mode this dependence also exists for most other parameters, such as remote access authorization.
Character mode
File names, etc. are seen in their character presentation. An Ä in a remote file name is for example understood in character mode in the partner system also as an Ä, even if different system coding is set there and different local coding is set. If the Ä is not included in the character set of the partner system, the command is aborted (e.g. "Syntax error in the resulting file name"). The character mode assumes that the partner is openFT V12.1 or higher.
The FTP protocol does not support the character mode.
Note on Windows systems
In Windows systems it is possible in character mode to specify remote file names and command strings in remote follow-up processing regardless of the locally set ANSI code; the character set - compared with that of Windows file names (UCS-2) - is not restricted. This even applies for local file names regardless of the selected mode.