If you are updating from a version of the extend Interoperability Suite prior to version 10.3.0, you need to be aware of the following changes that may affect your existing applications:
A new Windows feature called HIGHENTROPYVA is being enabled for this version of extend. It is an anti-hacking feature that randomizes load addresses and tends to put programs in the upper half of the x64 address space.
In extend 10.2.x, HIGHENTROPYVA was not supported; it was explicitly turned off. Now that it has been enabled, the result is that Windows x64 native object files compiled in version 10.2.x are now incompatible with the current runtime: you must recompile those programs before you can run them using the current runtime.
If you attempt to run an incompatible x64 program in extend 10.3.x, an error is generated, stating that the contained code is for a different processor family.
On Windows platforms, there has been an internal change to the way files are handled. This change should not have any adverse consequences to existing applications, but as a precaution, we recommend that you thoroughly test your applications in respect to file handling, to ensure that they still function as expected.
Also, as a consequence of the change, the following configuration variables are no longer applicable, and have been removed from the product:
In this release, when you use AcuServe, AcuRCL, Boomerang, or AcuToWeb you are prompted to select the AcuAccess to be used. When you select this for the first time, a new AcuAccess file is created, which includes some increased field size limit changes.
This new file is not backwards compatible with earlier versions of the above products. If you still plan to run older versions of AcuServe, AcuRCL, Boomerang, or AcuToWeb on your machine, we recommend that you take a copy of your existing AcuAccess file before you select it for use in the latest release of extend, and use the ACCESS_FILE variable to point to this file.
If you are using a dest-item of PIC 9(12) or larger, the format returned is the same as the FROM MICROSECOND-TIME clause; that is, there are now six decimal places for fractional second values: HHMMSSUUUUUU (Hours, Minutes, Seconds, Microseconds). To continue to use items of this size and still return a conventional value for the FROM TIME clause, compile your program with an earlier compatibility option, such as -c102.
The VTOP style, available for the radio button and check box controls, displays different behavior between the ACUCOBOL-GT runtime/thin client, and AcuToWeb - AcuToWeb behavior is as expected.