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)

Similar Messages

  • 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)

  • 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

  • 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's future

    Oracle have discontinued some of the less popular precompilers (Pro*PL/1, Pro*ADA and Pro*Fortran, I think). Does anyone know whether there have been any specific anouncements regarding the future lifespan of Pro*Cobol? I am interested from the perspective of both stand-alone programs and Forms User Exits. Where can I find this sort of information on Oracle's Web site?
    Thanks
    Phil

    I think as long as Pro*COBOL user exits ever WERE* supported on a given platform, and as long as FORMS is... they will continue to be supported.
    Mark
    *COBOL user exits were not supported on Windows, for example.                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • HT3053 Can I run my MacBook Pro Late 2008 without battery forever? Is it bad in long term or anything? Does it make the system less stable?

    Can I run my MacBook Pro Late 2008 without battery forever? Is it bad in long term or anything? Does it make the system less stable?
    My battery got swollen (and I unfortunately noticed it very late and might have be running with it for months, which potentially explains all the crashes everyday and the trackpad not working anymore, the Apple test also says I have a bar of ram broken...) and I had to remove it because the back pannel did not close anymore... Can I still use my MBP normally forever that way? I was planning on buying a new mac anyway but maybe waiting for the next iMac upgrade in the year... Should I wait?

    Other than the system shutting down instantly if you have a power outage, whcih could corrupt the OS. Nothing else bad will happen.

  • 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

  • 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?

  • Hi. my MacBook pro went off without me turnng it off. i tried turning it on again, but it wouldnt come on. i also tried doing the SMC thing, no avail. please any other thing to do ? (This notebook is still very new for anything to be wrong with it)

    hi. my MacBook pro went off without me turnng it off. i tried turning it on again, but it wouldnt come on. i also tried doing the SMC thing, no avail. please any other thing to do ? (This notebook is still very new for anything to be wrong with it).
    There is no way I would do the smc thing with a laptop that won't come on.

    If it's new and you're anywhere near an Apple Store, take it in. If it's less than 14 days old you can exchange it. If it's more they'll repair it for you.

  • Pro*Cobol for Oracle 10g Express Edition is available?

    Hi to all, this is my first post here.
    I evaluating Cobol to Oracle products and I have find one it´s more
    We installed Oracle 10g Express Edition (Server and Client), to test compatibility of a Cobol product.
    This product requires the "rtsora" component, from Pro*Cobol, but we didn´t find it in any place in the instalation packages.
    The documentation show the precompilers to be at $ORACLE_HOME/precomp but there is only two folders (admin and lib) with "ottcfg" files. Nothing more
    Searching this and anothers foruns, I became to think if the precompilers facilities, like Pro*Cobol, may be available to the 10g Express Edition for Linux, OR, if this is a feature available only to the Standart Editions (or Windows)?
    The instalation and users manuals appears to don´t distinguish the 10g standart from the Express Edition. Also, the Express Edition doesn´t ask for any kind of "customization oprtions" as I read about in another topics.
    Edited:
    1 - We are using this on Linux Ubuntu.
    2 - The Windows 10g Express Edition appears to be more complete, but I need to run this on Express Edition.
    Thanks in advance!
    (sorry bad english)

    There is no official communication on 11G express edition release date .
    You will have to wait and watch Oracle Official website for that .
    Also check this :
    http://news.techworld.com/applications/3203909/oracle-stalls-over-11g-express-release/
    http://pcworld.about.com/od/businesscenter/Oracle-Mum-on-11g-Release-2-1.htm
    Regards
    Rajesh

  • Macbook pro shows incorrect storage information on SSD.

    I am using a macbook pro. The storage information is shown wrongly. Control I shows the correct information but finder and space bar on the hard disk show incorrect storage information. Used space is actually 122 GB which is shown as 140 GB. Even omnidiskkeeper shows the breakup of 122 GB but the storage information summary shows 140GB.

       Re-index Macintosh HD.
       Spotlight reindexing will take a while to finish.
       System Preferences > Spotlight > Privacy
       http://support.apple.com/kb/ht2409

  • Pro*Cobol and DBMS_OUTPUT.PUT_LINE

    I am new to Pro*Cobol and had a simple question (I hope).
    I have a stored proc that contains DBMS_OUTPUT.PUT_LINE stmts
    and I can see those in SQLPlus (when serveroutput=on), but I do
    not see them when I call it from Pro*Cobol. Is there a
    precompiler setting or something I need to set?

    'Far as I know, you'll have to repeatedly call
    dbms_output.get_line in your Pro*Cobol program to
    get the server output generated by your stored procedure.
    Hope that helps.
    All the best
    Michael

  • PRO * COBOL with Oracle 9i

    We are in the process of Database upgrades and a pro*cobol program which was working in HP UX 11 / Oracle 7.3.4 was not working in HP UX 11 / Oracle 9i. We are getting the following error when trying to compile it (make) -
    sh: 11139 Memory fault(coredump)
    *** Error exit code 139
    Can anybody help me with this issue.

    I posted this in the wrong place. Please ignore this.

  • Pro*Cobol in VMS to Unix environment

    Please let me know if I can use my current Pro*Cobol programs in
    Unix environment. We are planning to convert our platform to
    Unix. Presently I am using DCL on VMS. Thanks in advance for all
    your answers
    null

    HI
    It will still support Cobol in order to cater to the clients who are still in mainframe systems and those clients who have their legacy systems in Cobol.
    Regards,
    Bibs

  • 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

Maybe you are looking for