![]() | File Handling |
As with all Micro Focus Beta Release products, Micro Focus cannot guarantee that the features and the functionality available in this product will be made available in the final release. Circumstances beyond our control might prevent us from including a specific feature, or we might find from customer feedback that we need other features to make the product successful.
Furthermore this Beta release might not contain all the functionality present in previous Micro Focus COBOL products, or features which we are aiming to include within this product might not be available at this point in time.
We would like to draw your attention to the on-disk file readme.1 in the /docs directory of your installation. This document annotates problems which have been found within this release. You should also refer to your Read This First document for important product information.
The following issues and limitations of using Server Express with third party software are known:
/lib/crt0_r.o -lc_r
.Server Express users wanting to migrate applications that call Oracle, but who do not use the OpenESQL functionality for Oracle access, may find the following information useful. This would include people using COBSQL. However, please note that this method is not recommended by Micro Focus and is not intended to overrule advice from Oracle on the subject. For more information about configuring and accessing your Oracle database, you should consult your Oracle documentation.
Although Oracle traditionally rebuilds a runtime so that the APIs it uses are available to COBOL, this approach is not the best way of making oracle8 and COBOL work together. Under Server Express, the best solution is to create a 'shared library' with the oracle8 support linked into it and have this loaded before the application starts. To do this, you need to:
This solution has several advantages over the existing method:
The traditional method of re-linking a runtime for Oracle uses the following type of command:
cob -x -e "" -o rtsora <oracle_extra_stuff>
Under Server Express on AIX, you could create a shared library called rtsora8_t.so with all the oracle libraries linked into it by using:
cob -zt -e "" -o rtsora8_t.so <oracle_extra_stuff>
where <oracle_extra_stuff are the libs/files/options taken from the makefile that builds rtsora, which may include the following types of options:
-lxxxx, -Ixxxx, xxxxx.o
Note: If the oracle support links in the 'C' startup modules crt0.o or crt0_r.o, these should be omitted by not linking them into the shared library.
Next you need to compile the main program with some extra directives:
INITCALL"rtsora8_t"
Use this to allow the oracle support shared library to be loaded before the first line of the program is executed.
SERIAL
Use this if the oracle8 support uses threading, to enable the application for use in a threaded environment.
If the program fails to execute due to rts error (173) on rtsora8_t.so, the runtime has been unable to find rtsora8_t.so.
Otherwise, if rts error 198 is generated on rtsora8_t.so, the runtime has not been able to load rtsora8_t.so into memory. This may be due to:
The last thing to do is to create a 'dummy' rtsora that points to rts32_t. You do this by creating a symbolic link, although strictly speaking you could just use cobrun/cobrun_t triggers. A dummy rtsora can be created as follows:
ln -s $COBDIR/bin/rts32_t `pwd`/rtsora
Now you can run applications under Server Express that call Oracle functions directly.
Functionality has been removed since the Object COBOL Developer Suite V4.1 product, and is not present in this product. For specific details, please see the chapter If You're Using..., which gives advice on how to migrate applications which used obsolete or changed components.
Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.
![]() | File Handling |