Prev: mainframe material
Next: oracle10g SQLBEX giving 114 with Oracle Dynamic SQL Method 4 (ora9 works well)
From: bine on 28 Jan 2008 10:57 On 24 Jan., 22:50, "Sergey Kashyrin" <s...(a)resqnet.com> wrote: > For Win x64 I had to patch Cobol program after preprocessor this way (sed): > s/02 SQL-SQLVSN PIC S9(18)/02 SQL-SQLVSN PIC S9(9)/ > /02 SQL-DUMMY/d > s/02 SQL-SQHSTL PIC S9(18)/02 SQL-SQHSTL PIC S9(9)/ > s/02 SQL-SQHSTS PIC S9(18)/02 SQL-SQHSTS PIC S9(9)/ > s/02 SQL-SQINDS PIC S9(18)/02 SQL-SQINDS PIC S9(9)/ > s/02 SQL-SQHARM PIC S9(18)/02 SQL-SQHARM PIC S9(9)/ hi Sergey, you got it! it seems the oracle-documentation is insufficient because for 10.2.0.3.0 as well as even 11g it only mentiones PIC S9(9) fields but we got the idea after metalink insisting that we try the sample10 in the $ORACLE_HOME/precomp/demo first. On AIX5.3-64bit was an include $ORACLE_HOME/precomp/public/bndsel.cob which consisted of some PIC S9(18) definitions (plus 2 new fillers :-) in the BNDDVAR and SELDVAR parts. we wouldn't have found that solution on SLES9 had we looked there because sample10 there fails as well (because the include is the old one from 9.2.0.4.0 32bit) who would have thought to try all sample*.pco again after having a successfully running application for some years now ... ;-( but anyway: I got a solution to our problem and oracle promised to open <Bug:6778490> DOC: PRO*COBOL PROGRAMMERS GUIDE SHOWS ONLY SQLDA FOR 32BIT PLATFORMS and everybody's happy again ;-)
From: Robert on 28 Jan 2008 20:58 On Mon, 28 Jan 2008 16:49:54 -0700, "Frank Swarbrick" <Frank.Swarbrick(a)efirstbank.com> wrote: >>>> On 1/25/2008 at 6:50 PM, in message ><t74lp3hal5fd63smm4jiukcgre24nfvtdf(a)4ax.com>, Robert<no(a)e.mail> wrote: >> On Fri, 25 Jan 2008 16:54:49 -0700, "Frank Swarbrick" >> <Frank.Swarbrick(a)efirstbank.com> >> wrote: >> >>>>>> On 1/24/2008 at 6:53 AM, in message >>><ou5hp3pv634r7l7ucevb7sllf76lr05391(a)4ax.com>, Robert<no(a)e.mail> wrote: >>>> >>>> SQLBEX means you are using Pro*Cobol, which is buggy and poorly >>>> supported by Oracle. >>>> Your best solution is to abandon Pro*Cobol , switch to OpenESQL. >>> >>>Is OpenESQL a Micro Focus product? >> >> Yes, and well supported by Micro Focus. The Open in its name is a >> misnomer, it's not open >> source. >> >>> Does it work with non-Micro Focus COBOL compilers? >> >> No. > >I asked because I wondered if it could be used with, say, OpenCobol. Guess >not. Ah well. In principle, the precompiler should work, but to be legal you'd need the Micro Focus run time library, which (I'm pretty sure) is bundled with the compiler's run time, which requires royalties. MySQL has an open source cobol precompiler. Another option is putting SQL in called C programs.
First
|
Prev
|
Pages: 1 2 Prev: mainframe material Next: oracle10g SQLBEX giving 114 with Oracle Dynamic SQL Method 4 (ora9 works well) |