Changes Affecting Version 10.1.1

If you are updating from a version of the extend Interoperability Suite prior to version 10.1.1, you need to be aware of the following changes that may affect your existing applications:

Translating OEM character sets

In the previous release, Unicode support was introduced for user input and output, and as part of the implementation, a new configuration variable (COBOL-CHARACTER-SET) was introduced, and the TRANSLATE-TO-ANSI configuration variable was removed. If your data was represented by an OEM character set, you would either need to determine the correct Microsoft OEM code page, then set COBOL-CHARACTER-SET to its identifier number or to OEM (or 1).

For ease of updating, we have reintroduced the TRANSLATE-TO-ANSI configuration variable, with the same semantics as in prior versions. However, it should be noted that having COBOL-CHARACTER-SET set to the default of ANSI, and TRANSLATE-TO-ANSI to TRUE, is less efficient than setting TRANSLATE-TO-ANSI to FALSE, and setting COBOL-CHARACTER-SET to OEM. The reason is that, in the former case, the runtime first translates OEM data to ANSI, then translates the ANSI date to UTF-16 to display it; and when accepting data, the runtime receives UTF-16 data, translates it to ANSI, and then translates again to OEM to return to the COBOL program. While in the latter case, the runtime translates the OEM data to UTF-16 directly (to display), and UTF-16 to OEM directly (to accept).