quote:

---

Originally posted by Simon Tobias
Hi Panos.

I think we'd be better discussing this on the Micro Focus forum, accessible
from http://www.cobolportal.com . :-)

It sounds like the operating mode of COBOL -- i.e. 32-bit or 64-bit --
doesn't match your Oracle environment. On AIX, there are separate 32-bit and
64-bit products. If you're getting 'bad magic number' errors, it sounds like
your COBDIR/LIBPATH/PATH setting may be pointing to the wrong Server Express
product.

It *does* matter whether you use procob -- the 64-bit Pro*COBOL -- or
procob32, as they will generate different code, including the sizes of
variables passed into/from Oracle as pointers. If you use the wrong procob,
you will get RTS114 errors at execution time.

Cobsql will, from SX 2.2 SP1 onwards, support 64-bit Pro*COBOL. This ensures
that the correct procob binary gets called for your COBOL working mode, i.e.
32-bit or 64-bit.

As you've specified SQLDEBUG, you should see the command invoked by Cobsql.
Could you tell me what that is please? Also, when compiling your program, if
you pass the -v flag (verbose), please tell me what gets displayed.

Thanks.

Simon.


"Panos Zotos" <pzotos@syntax.gr> wrote in message
news:42ebc.103917$Kc3.3377921@twister2.libero.it...
> I use :
>
> cob -t -g prog.cbl
>
> to create a multi-threaded program. My cobol.dir file includes
>
> confirm
> p(cobsql) csqlt=oracle8 sqldebug display verbose trace deb end-c
mode=ansi
> endp
>
> I then run the program using
>
> cobrun_t prog.int
>
> having first copied the rts I build on top of rts64_t
>
> The same scenario worked from the first time using the 32bit product.
>
>
> One thing I noticed today, is that the procob precompiler cannot be
relinked
> succesfully. When I try to run "relink precomp" to link all precompilers
> according to Oracle instructions, I get an error when procob is reached,
> mentioning a bad magic number. The strange part is that procob exists and
> works, although it does not vaildate as a 64bit application using cobfile
> (but anyway does it matter if procob is 32bit or 64bit since all it does
is
> to create cobol code with expanded sql statements...)
>
> Panos
>
>
>
> "Simon Tobias" <Simon.Tobias@nospam.microfocus.com> wrote in message
> news:c4jdvg$rvf$1@hyperion.microfocus.com...
> are
> fine!
Oracle[color=darkred]
> Oracle
up[color=darkred]
> in
> you're
>
>

---

quote:

---

Originally posted by Simon Tobias
Hi Wayne (and Panos)

Apologies if you're aware of some of this already, but I just wanted to
clarify the steps involved in creating and executing a Pro*COBOL application
with Micro Focus Server Express on UNIX.

When installing Pro*COBOL on UNIX (as part of the main Oracle installation),
you need to have your COBOL environment setup, in order for the installer to
relink a COBOL RTS containing the Oracle support libraries
(rtsora/rtsora32/rtsora64).

The 64-bit edition of Oracle 9i on AIX 5.x creates rtsora -- the 64-bit
version of the run-time -- and rtsora32 -- the 32-bit version of the
run-time.

It's imperative that you use the correct edition of Server Express, i.e.
32-bit or 64-bit -- note well, that these are separate products on this
platform -- for the mode in which you wish to use Oracle. In addition, you
need to ensure that LIBPATH is set to point to the correct Oracle 'lib'
directory -- $ORACLE_HOME/lib32 for 32-bit, or $ORACLE_HOME/lib for 64-bit

If you wish to recreate those executables, say if you've updated your COBOL
environment since installing Oracle, then from looking at the makefiles --
ins_precomp.mk and env_precomp.mk -- then the effective commands to use to
re-link the run-time correctly are as follows (logged in under your Oracle
user ID) :

either mode:
<set up COBDIR, ORACLE_HOME, ORACLE_BASE, ORACLE_SID as appropriate for your
installation>
export PATH=$COBDIR/bin:$ORACLE_HOME/bin:$PATH

32-bit :
export LIBPATH=$COBDIR/lib:$ORACLE_HOME/lib32:$LIBPATH
cd $ORACLE_HOME/precomp/lib
make LIBDIR=lib32 -f ins_precomp.mk EXE=rtsora32 rtsora32

64-bit:
export LIBPATH=$COBDIR/lib:$ORACLE_HOME/lib:$LIBPATH
cd $ORACLE_HOME/precomp/lib
make -f ins_precomp.mk rtsora

Regarding precompiling your application, Oracle provide two versions of
Pro*COBOL. Again, you need to use the correct one depending on whether
you're creating a 32-bit or 64-bit application, as the precompiler will
generate different code.

If invoking Pro*COBOL directly, you need to use :

32-bit : procob32 / procob18_32 , e.g.
procob32 myapp.pco
cob -it myapp.cob
rtsora32 myapp.int

or
64-bit : procob / procob18 , e.g.
procob myapp.pco
cob -it myapp.cob
rtsora myapp.int

If you're using Server Express 2.2 SP1 or later, you can also compile using
the Cobsql preprocessor, which will invoke the correct version of Pro*COBOL
under the covers, allowing for a single precompile-compile step, e.g.

cob -ik myapp.pco -C "p(cobsql) csqlt==oracle8 endp"

This method also aids debugging, as you will see the original source code
while animating, rather than the output from the precompiler. See the Server
Express Database Access manual. Prior to SX 2.2 SP1, Cobsql only supported
the creation of 32-bit applications.

I hope this helps -- if you're still having problems, please let me know.

Regards,
SimonT.

---

quote:

---

Originally posted by Simon Tobias
Hi Wayne.

On the surface, it appears as if you're not picking up the correct Pro*COBOL
binary.

If you invoke 'procob' from the command line, you should see something along
the lines of :

Pro*COBOL: Release 9.2.0.4.0 - Production on Mon Apr 19 13:38:07 2004

followed by a list of Pro*COBOL options.

Do you see this, or do you see a different banner (say, Pro*ADA, or
Pro*Fortran)? Assuming you see something other than a Pro*COBOL banner, then
if you invoke 'whence procob', does it show procob as being picked up from
your Oracle bin directory (/home/oracle/9.2.0/bin/procob in my case) ?

If you're either not seeing the correct Pro*COBOL banner, or it's not
located in the correct directory, I'd suggest rebuilding the procob and
procob32 binaries. Logged in under your Oracle user ID, with the Oracle
environment set up :

cd $ORACLE_HOME/precomp/lib
make -f ins_precomp.mk procob32 procob

and then try your compilation process again.

Regards,
SimonT.

---