The following applies for messages and output of openFT commands in the local system:
Unix systems
Messages and display output appear as before in local character code. Recoding does not take place. Exceptions: the output of a locally invoked ftshwc command, which is converted from UTF-8 to the locally set character code as of V12.1, as well as the output data streams when displaying remote file contents and when remotely executing commands (ftexec, ftadm, pre-processing); the local CCS specifications in the appropriate calls are regarded here as the target code.
If you change the local code setting, then you must also expect the output appearance of an openFT command to change. If for example an openFT request with the local file name "Köln" was called with UTF-8 as the local character code, and the character code changed in the meantime to ISO8859-1 when viewing the appropriate logging entry, the local file name now appears in the logging record as "KĶln".
Windows systems
Console output appears as wide characters (WideChar), i.e. in a UCS-2 character code internal to the operating system. This enables all the characters to be output that can be represented in the set graphic character set. This also applies for file contents, which are obtained via an ncopy command and output on stdout if UTF8 was specified as the local CCS name.
Messages and output that are rerouted to a file or pipe are output according to the environment variable OPENFTOUT as per the following rule:
OPENFTOUT = OLD | Output as before, i.e. in OEM for stderr or table output, and in local ANSI |
OPENFTOUT not defined | as OPENFTOUT = OLD |
OPENFTOUT = UTF8 | Output in UTF-8 |