Kbase 19513: Version 9, SCO OpenServer and the OSR Compat BCM
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
Version 9, SCO OpenServer and the OSRCompat BCM
FACT(s) (Environment):
Progress 9.x
SCO OpenServer 5.x
FIX:
Beginning with Version 9.0B, Progress has only one port to cover all UnixWare and SCO OpenServer platforms. In order to run Progress on SCO OpenServer, the OSRCompat Binary Compatibility Module (BCM) must be installed (as instructed in the Progress Installation Guide). The BCM is provided by SCO in order to allow programs compiled under UnixWare (typically UnixWare 7) to run on SCO OpenServer machines. The SCO UnixWare implementation and the SCO OpenServer implementation use different libraries and operating system calls. The BCM provides a mapping from the UnixWare calls to the OpenServer calls.
The mapping allows programs that are compiled under SCO UnixWare to execute properly on SCO OpenServer. The BCM is also required for the Java implementation on SCO OpenServer.
For more information, please refer to Caldera's web site.
The port that Progress runs on the SCO OpenServer is actually built on UnixWare. This is why the BCM is required in order to run Progress on SCO OpenServer.
The BCM installs into the /udk directory. This directory is where the SCO OpenServer/Unixware Development Kit (UDK) is installed. The UDK allows developers on SCO OpenServer and SCO UnixWare to write applications that are portable between the SCO OpenServer and UnixWare platforms.
According to the OSRCompat BCM documentation, the BCM provides a linker that allows executables to be linked. This is located in /udk/usr/css/bin. There is no requirement to install the full UDK in order to get the linker, according to the BCM documentation. For more information on this (in regards to using PROBUILD), please refer to Progress Solution 19437.