Enbedding PL/SQL function in Pro Cobol

HI,
I am trying to compile an existing pro cobol program because of a small enhancement. I am trying to embed a pl/sql function in to the program..and the compiler is throwing errors.Can someone please tell me what i am doing wrong? Please look at the piece of code that i added to the existing program.I have set the Oracle option sqlcheck = semantic...
exec sql execute
BEGIN
finddatatype(:ws-destination-tbl1,
:ws-destination-tbl-col-1,
:ws-data-type);
END;
end-exec
null

It's been a while since I used Pro*C but I think sqlcheck should be set to FULL not SEMANTICS for embedded PL/SQL.
Maybe this is the same for Pro*Cobol?

Similar Messages

Using WITH clause in Pro*Cobol

Hi!
I am trying to improve the performance of a query by introducing WITH clause.
The query is in Pro*Cobol Release 9.2.0.6.0 - Production.
I got compilation error
WITH DPTCOST AS (
...............1
PCB-S-00400, Encountered the symbol "DPTCOST" when expecting one of the following:
END-EXEC
....continued
So I wonder if we could use that clause at all with Pro*Cobol
Here is the excerp of the code
EXEC SQL
DECLARE INPUT_ACTUAL CURSOR FOR
WITH DPTCOST AS (
SELECT /*+ rule */
A.CODE_COMBINATION_ID,
A.SEGMENT1, A.SEGMENT2, A.SEGMENT3,
A.SEGMENT6,
D.COSTING, D.PROCESS,
D.MTL_CODE, D.FACTOR
FROM
GL_CODE_COMBINATION A,
ALCGL_DEPARTMENT_COSTINGS D
WHERE
A.TEMPLATE_ID IS NULL
AND A.SUMMARY_FLAG <> 'Y'
AND A.SEGMENT1 = D.PLANT_NUMBER
AND A.SEGMENT3 <> '6999001'
AND A.SEGMENT3 <> '6999002'
AND SUBSTR(A.SEGMENT2,4,3) = D.DEPARTMENT
AND D.ACTUAL_FLAG = 'A'
) ... continued

Materialized views are basically stored query results. They offer advanced functionality like query rewrite, refresh on commit, and more;
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_6002.htm
Unlike a view, they actually store the results of the query - not just the query;
SQL> create table t (cid number primary key)
Table created.
SQL> insert into t select object_id from dba_objects where object_id is not null
12791 rows created.
SQL> create materialized view mv
   as select * from t
Snapshot created.
SQL> select object_name, object_type from user_objects where object_name ='MV'
OBJECT_NAME                    OBJECT_TYPE
MV                             TABLE
MV                             MATERIALIZED VIEW
2 rows selected.
SQL> select segment_name, bytes from user_segments where segment_name in ('T', 'MV')
SEGMENT_NAME                        BYTES
T                                  196608
MV                                 196608
2 rows selected.Temporary tables are simply tables that are created then dropped. GLOBAL TEMPORARY TABLES have the advantage (or disadvantage) of only existing until commit or the end of the session. They results are visible to the user that inserted the data - but only temporarily;
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7002.htm#sthref7483

NVL2 in pro cobol giving the error.

For some reason we are getting an compiler error when we use NVL2 function in embedded sql statement in a pro-cobol module. Here is the output from the compiler. Do we have to add any options to recognize the new functions/keywords?
procob iname=vas107h2.pco include=/oracle/home/product/9.2.0/precomp/public ireclen=132 oreclen=132 sqlcheck=full ltype=none
" PICX=VARCHAR2 include=/jsbatch/vista/dev/cobol/cpy
Pro*COBOL: Release 9.2.0.7.0 - Production on Tue Oct 31 13:49:35 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
System default option values taken from: /oracle/home/product/9.2.0/precomp/admin/pcbcfg.cfg
Error at line 595, column 12 in file vas107h2.pco
EXEC SQL DECLARE DRIVER CURSOR FOR
...........1
PCB-S-00576, PLS-201: identifier 'NVL2' must be declared
Error at line 595, column 12 in file vas107h2.pco
EXEC SQL DECLARE DRIVER CURSOR FOR
...........1
PCB-S-00576, PLS-0: SQL Statement ignored
*** Error code 1
make: Fatal error: Command failed for target `vas107h2'
Thanks,

I'm not familiar with Pro*Cobol, but there's a similar issue with Pro*C, the parser does not recognize this built-in function. Given workaround is:
1) Use NVL() instead of NVL2().
2) Use Dynamic Sql in Pro*C. For example:
EXEC SQL EXECUTE
declare
v_var varchar2(100);
BEGIN
execute immediate 'select nvl2(user, user, 'N/A') from dual' into v_var;
END;
END-EXEC;
If that doesn't help, you should contact Oracle support.
Werner

Analytic Functions in Pro*C

Hi. Does anyone know if you can have analytic functions in Pro*C? I tried to compile this select statement and I get this error:
EXEC SQL DECLARE officer_cursor CURSOR FOR
SELECT opd,
nvl(rank1,0),
nvl(rank2,0),
nvl(rank3,0),
nvl(rank4,0)
FROM (SELECT aa.opd,
max(decode(rn,1,aa.tdrank,null)) rank1,
max(decode(rn,2,aa.tdrank,null)) rank2,
max(decode(rn,3,aa.tdrank,null)) rank3,
max(decode(rn,4,aa.tdrank,null)) rank4
FROM (SELECT o.workperson_id OPD, td.rank TDRANK,
ROW_NUMBER() OVER (PARTITION BY o.workperson_id ORDER BY td.rank) rn
FROM titleDOMAIN@REB_STEP_LINK TD,
OFFICER_TITLEDOMAIN@REB_STEP_LINK T_D,
OFFICER@REB_STEP_LINK O
WHERE COMPANY_ID = 835
AND TD.ID = T_D.TITLEDOMAIN_ID
AND O.ID = T_D.OFFICER_ID) aa
GROUP BY aa.opd ORDER BY aa.opd) zz
ORDER BY rank1, rank2, rank3, rank4;
END;
EXEC SQL OPEN officer_cursor;
Pro*C/C++: Release 8.1.7.1.0 - Production on Fri Aug 27 16:48:43 2004
(c) Copyright 2000 Oracle Corporation. All rights reserved.
System default option values taken from: ora_proc20:pcscfg.cfg
Syntax error at line 6779, column 28, file 10yr_sr_pub_extract.pc:
Error at line 6779, column 28 in file 10yr_sr_pub_extract.pc
ROW_NUMBER() OVER (PARTITION BY o.workperson_id ORDER BY td.rank) rn
...........................1
PCC-S-02201, Encountered the symbol "(" when expecting one of the following:
, into, from,
Error at line 0, column 0 in file 10yr_sr_pub_extract.pc
PCC-F-02102, Fatal error while doing C preprocessing
Thanks ahead of time.

Hello,
You don't say what version of Pro*C you are using, but I am guessing less than 11g. You may want to check out MetaLink Note:230115.1 (Precompiler Parsing SQL or PL/SQL Syntax Fails With PCC-02201 or PCB-00400). Essentially the precompiler does not "understand" some of the newer syntax. I believe the recommended option is to use dynamic sql as described in the Pro*C Programmer's Guide. There are a few bugs (notably 2471094 - PRECOMPILE FAILS WHEN USING OVER ANALYTIC CLAUSE) which are marked as fixed in version 11 - however I have not verified this.
Regards,
Mark

Pro*Cobol PCO Compilation problem in Linux

Hi,
DB :oracle 11g on RHEL 5.5
when we are compiling the (Pro*cobol ) PCO code it is giving us the error :
System default option values taken from: /oracle/oracle11g/app/product/11.2.0/dbhome_1/precomp/admin/pcbcfg.cfg
Error at line 320, column 35 in file BR2385.PCO
WHERE A.SOC_NO = :PARAM-SOC
..................................1
PCB-S-00223, Undeclared variable "PARAM-SOC".
when we change the pcbcfg.cfg file with flag : declare_section=no it's compile without error.
But in this scenario cobol app doesn't run.
if we declare the undeclared variable in the section
EXEC SQL BEGIN DECLARE SECTION END-EXEC.
PARAM-SOC PIC X(25).
EXEC SQL END DECLARE SECTION END-EXEC.
and compile it with declare_section=yes then cobol app. run fine.
Are different files generated (cob,int,gnt) after compilation with the option declare_section=no and declare_section=yes.
Pls help us in this regards. we have lot of file which having these issue and we don't want to do manual changes "EXEC SQL BEGIN" in it.
Thanks in advance..

Your code is faulty and has to be fixed.
No compilation problem is present, the compiler correctly barfs.
As this is not a support forum, kindly keep your non-issues out of this forum.
Thank you!!!
Sybrand Bakker
Senior Oracle DBA

Pro*Cobol on VMS

I'm interested in embedding SQL statements in COBOL programs running on VMS. However, all of the documentation that I see mentions running Pro*Cobol on Windows or the Micro Focus COBOL compiler.
How would I go about developing embedded SQL statements on VMS? I.e. do I have to pre-compile the files on a Windows box and then copy them over? Is this possible?
Thanks,
Josh

The HOST command in Forms can only call procedures on the client that runs Forms (assuming you run Forms in client/server mode, this is the user's PC).
If you want to run a procedure on the database host, you have to call this procedure from the database, not from Forms.
In 8i the easiest way is to do this via a Java stored procedure:
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:952229840241

Can't compile old Cobol Programs with Oracle9i Pro*Cobol.

I'm a Cobol and Oracle greenhorn - so please apologise my question.
Here are the details:
We want to switch our db from
Oracle8i Enterprise Edition Release 8.1.7.0.0
to
Oracle9i Enterprise Edition Release 9.2.0.4.0
If I have the "Oracle 8i client" installed on my developing system (using procob precompiler) my program compiles without problems. Connecting to our old 8i db works fine.
On connecting to our new 9i db my program crashes on the first EXEC SQL statement with:
114 Attempt to access item beyond bounds of memory
So I have installed the "Oracle 9i client" to use the new precompiler
Pro*COBOL: Release 9.2.0.1.0
BUT now I can't execute my program because procob inserts some CALL "ORASQL8" which doesn't exist in my Oracle installation. Maybe ORASQL9 would work, because there are some files with this name in my Oracle dir.
How can I make my NET Express Version 3.1.11 Service Pack 1 work together with Oracle9i?
Here are my current (old) Precompilersettings from the file cobol.dir:
p(cobsql) csqlt=ora8 cbl2ora8 sqldebug end-c ireclen=132 oreclen=132 maxliteral=160 picx=varchar2 p(cp) sy endp copyext (pco,cbl,cpy,cob) osext(pco);
This forum is my last resort. Maybe anyone can help?
Thanks in advance
lual

...solved by myself.
After wasting a lot of time, i've found a quick and dirty solution...
C:\oracle9i\bin\ORASQL9.DLL
duplicated and renamed to ORASQL8.DLL
C:\oracle9i\precomp\lib\msvc\oraSQL9.LIB
duplicated and renamed to oraSQL8.LIB
C:\oracle9i\precomp\lib\orasql9.lib
duplicated and renamed to orasql8.lib
...now my old programs run again without errors.
lual

Pro*COBOL precomp and .pco demos not installed

Hi,
I am new to the Oracle database.
Installing Oracle 9.2, Standard Edition - downloaded Disk1, Disk2 and Disk3 for Windows NT/2000/XP from the OTN downloads.
I have COBOL programmes with embedded SQL - I need the Pro*COBOL precompiler (procob).
It seems like Pro*COBOL did not get installed and I do not have the \procob\ demos folder under %ORACLE_HOME%\precomp\demo\. In fact, the only folder in the \demo\ folder is \sql\.
I have tried compiling my own COBOL programs, which use the COBSQL preprocessor to call the Oracle procob precompiler. I get the error message:
* CSQL-I-018: Invoking ORACLE8 Precompiler/Translator
'procob' is not recognized as an internal or external command,
operable program or batch file.
* CSQL-F-021: Precompiler did not complete -- Terminating
Are Pro*COBOL precompiler and the procob demos installed with the download version of Oracle 9.2? Where can I get them from?
Many thanks

Hi, me again.
The procob demos are not installed by default -- Standard installation.
With a Custom installation, Pro*COBOL is found under 'Oracle 9i Development Kit 9.x > Oracle Programmer 9.x > Optional Dependencies'. You have to check the box 'Show all components including required dependencies' on the Custom install dialog to be able to expand the components and see the Pro*COBOL precompiler under Optional Dependencies.
I will get to testing the procob demos now and post back the success/failure of the Pro*COBOL precompiler installation.

Pro Cobol Directive for setting autocommit.

From the Cobol application,
1. In some cases, I have execute the SQL Statements and commit the same immediately.
2. In some cases, I have to execute the SQL Statments but should not commit immediately.
The easiest way is setting autocommit on and off, at the required places.
I am using Pro Cobol to connect to Oracle DB. Could any one help on this?
Thanks,
Mahendra.

From the Cobol application,
1. In some cases, I have execute the SQL Statements and commit the same immediately.
2. In some cases, I have to execute the SQL Statments but should not commit immediately.
The easiest way is setting autocommit on and off, at the required places.
I am using Pro Cobol to connect to Oracle DB. Could any one help on this?
Thanks,
Mahendra.

Pro*COBOL not getting instaled on Fedora 14

Hi,
I have installed Oracle 11gr2 on Fedora 14 x86_64 system,. But the Pro*COBOL pre compiler which automatically comes with Oracle is not getting installed (Instead Proc is available. I dont know why). I have the entire application coded in embeded SQL-COBOL programs. I am stuck here, unable to preprocess my programs.
Please suggest me the procedure to resolve. Thanks in advance.
Note: In "Advanced Install" option I could not find "custom instal"l or a provision to select "precompilers" but other DBA related things found
Venkatesh Kudire
[email protected]

David,
Can you try passing in the 1.5 VM location manually as listed below
WorkshopInstaller.exe LAX_VM d:\bea\9server\jdk150_04\bin\java.exe
Can you also make sure that the 1.5 JVM value entry is the first entry in the PATH environment variable.
cheers
Raj

Pro*Cobol abort without information...

Hi,
we are using the Pro*Cobol Precompiler for embedded SQl in Cobol-Programs.
Today I got a program abort without a helpful message (please see below).
Is there a possibilty to get more informations from the Pro*Cobol?
The program abort:
Pro*COBOL: Release 10.2.0.1.0 - Production on Do Mrz 14 11:34:50 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
System-Standardoptionswerte aus: /oracle/HMOT/precomp/admin/pcbcfg.cfg
PCB-I-0556: Abbruchfehler. Vorherige Fehlerbedingungen auflösen und Vorkompilierung erneut durchführen
It means:
PCB-I-0556: Unrecoverable error. Fix previous errors and re-precompile
Thanks and Regards,
Michael

Not the correct forum for your question - this one deals with general RDBMS questions. Not general Oracle product questions.
Have a look at the manual and at precompiler settings. By default ERRORS=YES, which means full error listing to the terminal when compiling. If this is set to NO, you will need to look in the log file for full error details. From your description, this setting would seem to be set to NO.
Or this is how I understand from my quick look at the Pro*COBOL® Programmer's Guide. (documentation portal at http://tahiti.oracle.com)

Pro*Cobol aborts without errormessage

Hi,
we are using the Pro*Cobol Precompiler for embedded SQl in Cobol-Programs.
Today I got a program abort without a helpful message (please see below).
Is there a possibilty to get more informations from the Pro*Cobol?
The program abort:
Pro*COBOL: Release 10.2.0.1.0 - Production on Do Mrz 14 11:34:50 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
System-Standardoptionswerte aus: /oracle/HMOT/precomp/admin/pcbcfg.cfg
PCB-I-0556: Abbruchfehler. Vorherige Fehlerbedingungen auflösen und Vorkompilierung erneut durchführen
It means:
PCB-I-0556: Unrecoverable error. Fix previous errors and re-precompile
Thanks and Regards,
Michael

Not the correct forum for your question - this one deals with general RDBMS questions. Not general Oracle product questions.
Have a look at the manual and at precompiler settings. By default ERRORS=YES, which means full error listing to the terminal when compiling. If this is set to NO, you will need to look in the log file for full error details. From your description, this setting would seem to be set to NO.
Or this is how I understand from my quick look at the Pro*COBOL® Programmer's Guide. (documentation portal at http://tahiti.oracle.com)

Environnement with pro-cobol and linux redhat

Hi,
I have a linux redhat Linux 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux
and oracle 11g database where we have installed Pro-cobol with a launcher xframe ( not me !)
we want to use command-line with pro-cobol :
exemples :
export COBOLOPTS="-dy -shared -M -lxconv -L$XFRAMEHOME/lib -I $PWD -WC,""DLOAD"" -WC,""SOURCE"" -WC,""COPY"" -WC,""XREF"" -WC,""FLAG(E)"" -WC,""MODE(STD)"" -WC,""ALPHAL(WORD)"" -WC,""NOTRUNC"" -WC,""NOSDS"" -WC,""SRF(FIX)"" -WC,""MAP"" -do ./ -dp ./ "
cobol -o OV1SLSP.e OV1SLSP.pre OV1MADR0.o $ORACLE_HOME/precomp/lib/cobsqlintf.o OV1MADR1.pre.o OV1MSNT0.pre.o 2> OV1SLSP.errors
execution:
OV1SLSP.e
results
Erreur de segmentation
we have a this error.
but when we use xframe launcher :
execution:
xrun OV1SLSP
results
XRUN: STARTING OV1SLSP
OV1MADR0 PLANTAGE SQL RNVP : -1012
SQLERRMC ORA-01012: non connecté
COBOL:rts: HALT: JMP0015I-U [PID:000004A0 TID:B7FFC940] CANNOT CALL PROGRAM 'COBCANC'. xvsamRts: undefined symbol: COBCANC PGM=OV1MADR0
XRUN: TERMINATED WITH CODE 134
=>This message is normal because we have connect to database !
It's working perfect.
My question is : what is the correct librairies to have to make static compiling pro-cobol's programs?
hope to be cleared.
Thanks.
Edited by: french_dam on 28 janv. 2011 10:07
Edited by: french_dam on 28 janv. 2011 10:11

Have you checked the system requirements for using Pro-Cobol with Oracle 11g and Linux? See here:
Pro*COBOL® Programmer's Guide 11g Release 1 (11.1)
http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28428/pcoabops.htm#insertedID1
Hope this helps,
Ben

RDBMS 7.3에서의 PRO*COBOL 사용 방법

제품 : PRECOMPILERS
작성날짜 : 1997-02-27
Platform : Sun Solaris V2.5.1
Version : Oracle V7.3.2.1
Pro*Cobol V1.8.2 or later
MF COBOL V3.2.20 or V4.0.05
RDBMS 7.3에서 PRO*COBOL 사용 방법
======================================
1. 환경설정 및 점검단계
(사용자가 csh을 사용할 경우를 예로 든다)
(1) ORACLE사용자로 login한 후, sample program이 있는 directory로 간다.
     # cd $ORACLE_HOME/precomp/demo/procob
(2) MF COBOL 사용을 위한 환경변수를 설정한다.
     # setenv COBDIR /usr2/mfcob
     # set path=($path /usr2/mfbin)
     # setenv LD_LIBRARY_PATH $COBDIR/coblib
(3) 먼저 실행 module이 생성되어 운용이 잘되는가를 확인한다.
     # make -f procob.mk build COBS=sample1.cob EXE=sample1
     혹은
     # make -f procob.mk sample1
     => sample1 실행 module이 작업 directory내에 생성된다.
     # sample1
** 이 단계에서 이상이 없으면 다음단계로 넘어가고,
     동작이 되지않으면 Pro*COBOL의 version및 기타사항을
     점검하여야 한다.
2. 작성한 program을 실행 module로 생성하여 운용하는 방법
# make -f procob.mk build COBS=<prog_name>.cob EXE=<prog_name>
# <prog_name>
3. 새로운 RTS를 생성하여 program을 실행하는 방법
(1) 새로운 runtime system인 rtsora를 생성한다.
     # cd $ORACLE_HOME/precomp
     # make -f ins_precomp.mk rtsora
     # cp $ORACLE_HOME/bin/rtsora $ORACLE_HOME/bin/rtsora_old
     # cp rtsora $ORACLE_HOME/bin
(2) Embedded SQL문이 포함된 <pro_name>.pco source program을
아래와 같이 compile한 후 새로운 runtime system인 rtsora에서
실행한다. 이때 <pro_name>의 실행module을 제거하여야 한다.
     # make -f procob.mk <pro_name>.cob
     # make -f procob.mk <pro_name>.gnt
     => <pro_name>.gnt module이 생성된다
     새로운 rtsora에서 실행한다 =>
     # rtsora <pro_name>

Dear Insaponata ,
I dont understand what do you mean by oneoff but see the following:
A patch is a one-off fix for a specific issue. The patch may be a manual process, or applied using the opatch utility. These changes may not result in an oracle version change, so it is only possible to tell that they have been applied by keeping a manual record, or by listing the patches applied via opatch, assuming that is how you applied them. Patches may have specific dependencies, so you must check you have the correct patch for your version.
A patchset is a collection or bundle of patches. Typically, a patchset is a more major operation, and as such will include be applied using the Oracle Universal Installer. The patchset will typically result in a significant version change, like 10.2.0.1.0 to 10.2.0.2.0 etc. Patchsets are usually cumulative, so you can patch anything from the base version release to the latest patchset in one go. So the same 9.2.0.8.0 patchset will be used to patch 9.2.0.1.0 and 9.2.0.7.0.
The word bundle implies a collection of patches, but a bundle may not be as big or important as a complete patchset. The bundle simply implies there are multiple patches bundles together.
I get this from this link:
http://www.araboug.org/ib/index.php?showtopic=25466
Mohamed

PRO*COBOL/Oracle 9.2 Error

I am trying to run a COBOL program using SQL. The program is pre-compiled with PRO*COBOL and the then with Microfocus NET Express. At runtime i get the following error.
$ ./testsample
Execution error : file 'sample1'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 10)
HP/MF COBOL Version: B.13.45
HP-UX hptest B.11.11 U 9000/800
pid: 22012 gid: 102 uid: 104
Thu Nov 21 19:03:12 2002
7:03pm up 36 days, 6:23, 34 users, load average: 0.28, 0.16, 0.13
Thread mode: No Threads
RTS Error: COBOL
Sync Signals: COBOL
ASync Signals: COBOL
cobtidy on exception: False
I get the same error with the sample program. Any idea what the cause may be?

Hello,
Reason: Your data might contain some foreign characters [non-english] ie., your server nls_lang settings might be different to the client nls_lang settings, as a result the new nls_lang characters will occupy extra bytes because of which even though it is apparent that you are using around 2000 bytes you may be using more than 4000 bytes. Examples Japanese characters seem to take 2 bytes per character, similarly russian takes 3 bytes per character.
The ojdbc14.jar seems to be doing some check on this and if the characters are more than 4000 bytes it gives u the ora-01461 error but the new 10G ojdbc14.jar allows this.
On the other hand you may be genuinely trying to insert more than 4000 bytes characters into varchar [example trying to insert the text values into a varchar()]
You may want to try this:
* Please download ojdbc14.jar from
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.htmla>
* Replace the old $omwb_home/lib/ojdbc14.jar with the ojdbc14.jar that you have downloaded in the step above.
Try a capture now.
Thank you.
Srinivas

Enbedding PL/SQL function in Pro Cobol

Similar Messages

Maybe you are looking for