The first COBOL call to the new client modules fails with RTS 114 and a telephone rings at Micro Focus SupportLine shortly thereafter. Everything was set up to compile, link, and run in 32 bit mode in the previous version, but 9.x is 64 bit by default. They upgrade OracleÂ, a data base product from Oracle Corporation, from version 8.x to 9.x. Several customers have created this problem for themselves in the same way recently. The call can be made, but the only possible outcome is an immediate RTS 114 error. Thus it is possible to have a 32 bit main program call a 64 bit shared object and vice versa. If the main program makes a dynamic call which will be resolved at run time, the linker does nothing to resolve the name during the linkage process. dll objects), cannot catch the problem while linking the main application. However, the more modern method of dynamic calls to callable shared objects (functionally similar to Windows. Even though the linker messages are not especially clear, the bad code never gets a chance to run. When statically linking applications into a single, monolithic executable, the system linker ("ld" command) will catch "mix and match" errors and report them with rather cryptic messages such as "wrong elf class" or "bad magic number". However, the UNIX operating system cannot handle a mixture of 32 and 64 bit code in the same application. On hardware which has the capability, Server Express can compile your COBOL source to either 32 bit or 64 bit code. The most common reason for RTS 114 errors reported on UNIX systems came into being with the ability to create and use callable shared objects.
0 kommentar(er)
