Migrating applications after system fallback

The modules that were generated on R3.5 are no longer compatible after a system fallback to an earlier release. Therefore, all such modules must be recompiled after system fallback.

An alternate method is to save a copy of the modules before system upgrade and then reinstate that copy after fallback. This method is applicable for the following scenarios:

• If the database layout after the fallback is similar to the layout before the system upgrade.

• If the application executables are not pre-processed, language-compiled and linked on 3.5.