• RELEVANCY SCORE 4.75

    DB:4.75:Problems With Pro*Cobol On 10g xk




    Hi ,
    We are trying to migrate from 9i to 10g. We were using pro*cobol 1.8. Now we are facing many problems while compiling and running these programs on Pro*COBOL: Release 10.2.0.2.0.

    Are there any migration guides available which might have the specific changes to be done.

    Thanks
    Akhila

    DB:4.75:Problems With Pro*Cobol On 10g xk

    Hi ,
    We are trying to migrate from 9i to 10g. We were using pro*cobol 1.8. Now we are facing many problems while compiling and running these programs on Pro*COBOL: Release 10.2.0.2.0.

    Are there any migration guides available which might have the specific changes to be done.

    Thanks
    Akhila

  • RELEVANCY SCORE 3.62

    DB:3.62:Pro C And Pro Cobol jx




    Enterprise Linux Enterprise Linux Server release 5.4 (Carthage)
    Kernel 2.6.18-164.el5PAE on an i686

    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options

    i am going to migrate a oracle 8i database to 10.2.0.1.0/ Redhat Linux

    what are the steps to be carried out in 10g environment for
    pro c pro cobol compatibility?

    santhanam.

    DB:3.62:Pro C And Pro Cobol jx

    Enterprise Linux Enterprise Linux Server release 5.4 (Carthage)
    Kernel 2.6.18-164.el5PAE on an i686

    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options

    i am going to migrate a oracle 8i database to 10.2.0.1.0/ Redhat Linux

    what are the steps to be carried out in 10g environment for
    pro c pro cobol compatibility?

    santhanam.

  • RELEVANCY SCORE 3.58

    DB:3.58:Cobol Precompiler 10g fa




    Hi there,

    I am upgrading from Oracle 9i to Oracle 10g.

    I decided to do a clean install by removing 9i and then installing 10g as a new thing.

    I can't however find an option to install the COBOL precompiler Pro Cobol.

    Can someone please tell me how to install this please?

    DB:3.58:Cobol Precompiler 10g fa

    hi,
    I have the same problem.
    We are trying to install Procobol on 10g Release 2.

    Where is the option to install it?

    Regards
    Akhila

  • RELEVANCY SCORE 3.51

    DB:3.51:Pro*Cobol/Oracle 9.2 Error xc


    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?

    DB:3.51:Pro*Cobol/Oracle 9.2 Error xc

    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?

  • RELEVANCY SCORE 3.45

    DB:3.45:Please Help! cz


    This may not be the right forum or even the right domain. But I really need help in understanding one particular error....and I need some resources in general to better understand how to work with the Sun machine.

    My background is working on IBM mainframe AS/400 systems. Our company also uses MicroFocus COBOL, MTP, and UNIX on a Sun Solaris system. I struggle to get problems resolved on the Sun system due to lack of program dump information and the extremely cryptic error messages.

    Can someone direct me to a domain, a support center, a manual (preferably online), a forum, or whatever to help me understand COBOL program failures? Often all I get is an "error code 255"? What the heck is that?!

    My immediate problem is this (again, maybe you can refer me to resources that will help me understand fix these problems in the first place). I have a MicroFocus COBOL program that is getting the error listed below. It's been suggested that the problem is that the program must be executing a STOP RUN instead of a GOBACK. That is not the case. Where can I turn to figure this problem out?

    I don't mean to offend any Sun fans out there - I am frustrated with my lack of knowledge more than anything else. Thank you!

    01/03/2005 23:51:28 unikixvsam19:KIX1245I Process signal-terminated -- Signal=11

    01/03/2005 23:51:28 unikixvsam19:received signal_2=11

    01/03/2005 23:51:28 unikixvsam19:COBOL TERMINATION ROLLBACK

    01/03/2005 23:51:28 unikixvsam19:KIX3801E [kx_handle_signal] Signal [11 ] received; exit process already entered

    01/03/2005 23:51:32 unikixvsam19:KIX0301I Entering (VER. 7.2.0p3 - 04/16/2002 )

    DB:3.45:Please Help! cz

    This may not be the right forum or even the right domain. But I really need help in understanding one particular error....and I need some resources in general to better understand how to work with the Sun machine.

    My background is working on IBM mainframe AS/400 systems. Our company also uses MicroFocus COBOL, MTP, and UNIX on a Sun Solaris system. I struggle to get problems resolved on the Sun system due to lack of program dump information and the extremely cryptic error messages.

    Can someone direct me to a domain, a support center, a manual (preferably online), a forum, or whatever to help me understand COBOL program failures? Often all I get is an "error code 255"? What the heck is that?!

    My immediate problem is this (again, maybe you can refer me to resources that will help me understand fix these problems in the first place). I have a MicroFocus COBOL program that is getting the error listed below. It's been suggested that the problem is that the program must be executing a STOP RUN instead of a GOBACK. That is not the case. Where can I turn to figure this problem out?

    I don't mean to offend any Sun fans out there - I am frustrated with my lack of knowledge more than anything else. Thank you!

    01/03/2005 23:51:28 unikixvsam19:KIX1245I Process signal-terminated -- Signal=11

    01/03/2005 23:51:28 unikixvsam19:received signal_2=11

    01/03/2005 23:51:28 unikixvsam19:COBOL TERMINATION ROLLBACK

    01/03/2005 23:51:28 unikixvsam19:KIX3801E [kx_handle_signal] Signal [11 ] received; exit process already entered

    01/03/2005 23:51:32 unikixvsam19:KIX0301I Entering (VER. 7.2.0p3 - 04/16/2002 )

  • RELEVANCY SCORE 3.44

    DB:3.44:C/Cobol Interoperability 1j


    Hello all,

    I'm currently looking into possibilities of combining COBOL and C code in a project.

    Services are written in COBOL and buffer type in use is FML32 which is converted to/from VIEW32 by means of FVFTOS32/FVSTOF32 calls from COBOL code. This works fairly well.

    However, I'm currently looking into using a C "hook" that the COBOL code would call in order to deal with a few things that are difficult to do from COBOL (checking or adding specific things in the FML32 buffer that may not fit in the view). While I'm working with the FML buffer, I thought it might be a good idea to actually do the buffer conversion from the C code. But it seems to me that FVSTOF32 and Fvstof32() differs somewhat.

    If I supply the FML buffer and the cobol view record to my C function and call Fvstof32(), all dec_t fields seem to turn into 0.0. Strings seem to work OK, though.

    Is this to be expected? Are there fundamental differences between FVSTOF32 and Fvstof32(), or is it the COBOL record / C structure that are different, especially with regards to the dec_t type?

    Any input on this welcome,

    /Per
    ---
    Per Lindstrom R2Meton AB, SWEDEN

    DB:3.44:C/Cobol Interoperability 1j

    Ed,

    many thanks for the clarification. In COBOL though, I guess the advantage is smaller, given the description found in
    http://e-docs.bea.com/tuxedo/tux90/pcb/pbenv.htm:
    dec_t(m, n) = S9(2*m-(n+1),n)COMP-3
    as m is "less than 10"
    (http://edocs.beasys.com/tuxedo/tux90/rf5/rf5j.htm#1531496)
    would give (for dec_t (9,0))
    S9(17) COMP-3
    or 17 digits of accuracy, which is not much more than the 15 digits I would be able to squeeze out of a double.

    I guess the 31-32 digits of accuracy you mention are only "reachable" when using the dec_t struct and decimal(3) C functions (which I could call from a COBOL program, but if FVFTOS32 don't deal with them I would still be out of luck). Please correct me if I'm wrong here.

    Best regards,
    /Per
    ---
    Per Lindstrom R2Meton AB, SWEDEN

  • RELEVANCY SCORE 3.39

    DB:3.39:Cobol Compile With Cc&Amp;B On Windows Xp 7s


    Hello,

    Could any one let me know how to compile COBOL program in CCB 2.3.0 installed on Windows XP?

    Edited by: user10609372 on Oct 7, 2010 12:20 PM

    DB:3.39:Cobol Compile With Cc&Amp;B On Windows Xp 7s

    Look for the file buildPrompted.bat

    Run it and supply the COBOL file name you want to compile.

    Generated listings etc can be found in env\cobol\build

  • RELEVANCY SCORE 3.38

    DB:3.38:Legacy Cobol Application On Windows 2008 Server Enable Caching cx


    I have a legacy application that was created in Cobol, sometime the application has some problems of disconnections, files corruptions and sometimes is very slow. i have the appl on a windows server 20008 with 4gb ram and raid 1. should I destroy the
    raid 1 and enable the disk caching? what are the recommendations and the best configuration?

    thanks

    DB:3.38:Legacy Cobol Application On Windows 2008 Server Enable Caching cx

    Hi,
    It’s hard to say that the raid 1 cause the issue. It can cause the legacy application has compatible issue with the new OS. In order to narrow down the issue, you may check in the task manager to see which process takes the memory resources.
    In addition, you can also use reliability and performance monitor to track down what cause the performance issue.
    Windows Reliability and Performance Monitor
    http://technet.microsoft.com/en-us/library/cc755081(WS.10).aspx
    Windows Performance Monitor
    http://technet.microsoft.com/en-us/library/cc749249.aspx

    Best Regards,
    AidenAiden Cao
    TechNet Community Support

  • RELEVANCY SCORE 3.34

    DB:3.34:Cobol And Java a1


    I have a servlet running in BEA Weblogic Server on Unix machine. I want to add some computing functionallity.
    I have this computing program already written in cobol. It is a very large program(20000 lines of code)
    Does anyone have suggestions have to integrate this cobol program into the java/unix environment?.
    I have seen some uses Runtime.exec() but how is performance with this method? Anyone experience with this?

    DB:3.34:Cobol And Java a1

    Performance depends on what the COBOL program does/how it is used. If your java program only needs to call COBOL once in a while, then your application can probably tolerate the overhead of starting a separate process each time.

    Other consideration: If the interface between the java program and the COBOL program is extensive (i.e. requires lots of data to be passed back and forth), then you may have to introduce more overhead, either in generating and processing stdin/stdout, or in passing data through files.

    Can't help you with other methods to call COBOL. Native methods are C methods. If there is a way to call the COBOL program from C, well then there is probably a way to build a bridge from java.

  • RELEVANCY SCORE 3.30

    DB:3.30:Can I Use Timesten With Cobol? 98


    Can I use TimesTen with Cobol?

    DB:3.30:Can I Use Timesten With Cobol? 98

    Hi Chris,Thanks a lot for your help.Regards,Amol Shinde

  • RELEVANCY SCORE 3.23

    DB:3.23:Pro Cobol For Oracle 9 On Linux jz


    Is there support for (pro) cobol for Oracle 9 on a linux server?
    The current application runs on HP-UX and uses Oracle 9. Pro cobol is required.

    We want to migratie the oracle server to Linux (suse)

    regards,

    peter

    DB:3.23:Pro Cobol For Oracle 9 On Linux jz

    Is there support for (pro) cobol for Oracle 9 on a linux server?
    The current application runs on HP-UX and uses Oracle 9. Pro cobol is required.

    We want to migratie the oracle server to Linux (suse)

    regards,

    peter

  • RELEVANCY SCORE 3.22

    DB:3.22:Pro*Cobol, Pl/Sql Package, Utl_File.Invalid_Operation 1s


    Hello,

    Environment:
    Oracle Enterprise Edition 9.2.0.6.0 - 64 bit
    Not sure of UTL_FILE version
    SunOS 5.0, Generic May 2002
    Pro*Cobol 1.8.77.6.0

    I have a Pro*Cobol program calling a PL/SQL Package which tries to execute a UTL_FILE.FOPEN operation. When the UTL_FILE.FOPEN operation is attempted, a "When utl_file.invalid_operation" exception occurs.

    If I run the Package within an anyonomus block from Sql*Plus or PL/SQL Developer, the Package and its various UTL_FILE operations (fopen, is_open, get_line, fclose) run to completion successfully.

    I've searched OTN Forums and google for Cobol and Utl_File.Invalid_Operation. I've gotten hits on either Cobol or Utl_File.Invalid_Operation but not the two together.

    Has anyone encountered something like this? If so, was there a solution? Could Permissions be involved?

    Thanks

    Message was edited by:
    mnbvcxz
    Corrected Oracle DB version

    DB:3.22:Pro*Cobol, Pl/Sql Package, Utl_File.Invalid_Operation 1s

    Thank you for the ideas.
    The Pro*Cobol syntax I'm using to call the package is:
    EXEC SQL EXECUTE
    BEGIN
    name_of_package.name_of_routine (parm1, parm2, etc.);
    END;
    END-EXEC.Parm1, Parm2, etc. are Varchar2(20) variables defined as PIC X(20) in the COBOL program.

    The anonymous pl/sql block looks like:
    DECLARE
    l_parm1 varchar2(20) := 'some value';
    l_parm2 varchar2(20) := 'some other value';
    BEGIN
    name_of_package.name_of_routine (parm1, parm2, etc.);
    END;I think the COBOL program is connecting to the Oracle database with the same User Name as when I run the pl/sql block from Sql*Plus because there are some SELECT's in the package which are successfully executed before hitting the UTL_FILE.FOPEN error.

    It's probably some kind of permissions issue related to my Unix logon versus what UTL_FILE.FOPEN is trying to do. Possibly it has something to do with permissions on our Oracle Directory Object used in the FOPEN command.

  • RELEVANCY SCORE 3.18

    DB:3.18:Procobol Segmentation Fault 7k


    I am getting a segmentation fault when trying to compile my program. Any ideas?

    The Oracle base for ORACLE_HOME=/home/oracle/10G is /home/oracle/10G
    make -f Makefile build COBS=PROGNAME.cob EXE=PROGNAME
    make[1]: Entering directory `/h/steve/cobol/gen/target'
    procob sqlcheck=syntax include=. include=../dbfields include=../COPYBOOK userid=
    steve/steve iname=PROGNAME.pco

    Pro*COBOL: Release 10.2.0.1.0 - Production on Mon Mar 9 11:04:41 2009

    Copyright (c) 1982, 2005, Oracle. All rights reserved.

    System default option values taken from: /home/oracle/10G/precomp/admin/pcbcfg.c
    fg

    PCB-W-0006: Userid only used when SQLCHECK=FULL, userid ignored.
    make[1]: *** [PROGNAME.cob] Segmentation fault
    make[1]: Leaving directory `/h/steve/cobol/gen/target'
    make: *** [PROGNAME] Error 2

    Edited by: steve_rainbird on Mar 9, 2009 1:14 PM

    DB:3.18:Procobol Segmentation Fault 7k

    I am getting a segmentation fault when trying to compile my program. Any ideas?

    The Oracle base for ORACLE_HOME=/home/oracle/10G is /home/oracle/10G
    make -f Makefile build COBS=PROGNAME.cob EXE=PROGNAME
    make[1]: Entering directory `/h/steve/cobol/gen/target'
    procob sqlcheck=syntax include=. include=../dbfields include=../COPYBOOK userid=
    steve/steve iname=PROGNAME.pco

    Pro*COBOL: Release 10.2.0.1.0 - Production on Mon Mar 9 11:04:41 2009

    Copyright (c) 1982, 2005, Oracle. All rights reserved.

    System default option values taken from: /home/oracle/10G/precomp/admin/pcbcfg.c
    fg

    PCB-W-0006: Userid only used when SQLCHECK=FULL, userid ignored.
    make[1]: *** [PROGNAME.cob] Segmentation fault
    make[1]: Leaving directory `/h/steve/cobol/gen/target'
    make: *** [PROGNAME] Error 2

    Edited by: steve_rainbird on Mar 9, 2009 1:14 PM

  • RELEVANCY SCORE 3.17

    DB:3.17:Tuxedo With Xa Connection On Oracle 8.1.6 On Hpux 11 ap



    Hello,
    I search informations (references, problems, experiences, tests ...) on a configuration with tuxedo with xa connection on oracle 8.1.6 with cobol programs.

    Thanks

    DB:3.17:Tuxedo With Xa Connection On Oracle 8.1.6 On Hpux 11 ap

    You will likely not find too many answers for tuxedo questions on these
    newsgroups. I suggest contacting your sales representative who can give you
    more assistance.

    Thanks,
    Michael

    --
    ----
    Michael Girdley
    BEA Systems Inc

    "Jean-Guy Maisonneuve" jean-guy.maisonneuve@icdc.caissedesdepots.fr wrote
    in message news:399ab9a5$1@newsgroups.bea.com...

    Hello,
    I search informations (references, problems, experiences, tests ...) on aconfiguration with tuxedo with xa connection on oracle 8.1.6 with cobol
    programs.

    Thanks

  • RELEVANCY SCORE 3.17

    DB:3.17:Microfocus Cobol License m9


    After applying PeopleTools 8.49.09 patch , microfocus cobol license expired . It is not valid . Cannot start any PS cobol programm. I used : ORACLE-30DAYDEV32 trial license . When i try to recompile cobol with ./pscbl.mak , than get error LMF-006 . How to solve this problem ?

    DB:3.17:Microfocus Cobol License m9

    I suggest to open a case with CSC immediately. They would provide you with the right license key.

    I hope it is not production environment. In any case fixing it before it is done in production.

    Cheers.
    RD

  • RELEVANCY SCORE 3.14

    DB:3.14:Where Can I Download Pro*Cobol For Oracle Database 11g ? zf


    Where can I download PRO*COBOL for Oracle database 11g ? I have downloaded installed linux.x64_11gR1_database_1013.zip
    It has a procob32 but it gives an ERROR loading shared library libcIntsh.so.11.1 ?
    What should pro*cobol be for my linux 64 bit AMD ? (procob procob32, procob18, procob64)
    Hope somebody can help with this, Thanks, owen@uvsoftware.ca www.uvsoftware.ca

    DB:3.14:Where Can I Download Pro*Cobol For Oracle Database 11g ? zf

    This is not the appropriate forum to post this.

    Kindly post it in the Database General Forum or search in the download section.

    Regards.

    Satyaki De.

  • RELEVANCY SCORE 3.14

    DB:3.14:How To Use Pro*Cobol With Rmcobol d3


    Hi,

    I try use Pro*Cobol with RMCobol compiler.
    But I have problem to use oraSQL9.LIB y with runcobol (runtime).
    Thank for any help.

    DB:3.14:How To Use Pro*Cobol With Rmcobol d3

    Just for those interested PRO*COBOL is now available with RM/COBOL V8 and ORACLE 8/9i for Windows.

    I expect that a version for Unixware 7 and Linux to be available later this year, and eventually a version for Aix 4.2/4.3 also with Oracle 8/9.

    For further info please contact me at
    frederico_fonseca at syssoft-int.com

    Regards

    Frederico Fonseca

  • RELEVANCY SCORE 3.04

    DB:3.04:Dataqueue On As400 From Java To Cobol 3a


    my java prog is called by a cobol prog with params and
    should return a 16char-string to the cobol prog.
    we will do that now with a dataqueue.
    tell me please how to use a dataqueue.
    or is there an easier possibility?

    string main(..)
    ...
    return string;

    doenst work

    DB:3.04:Dataqueue On As400 From Java To Cobol 3a

    Get the AS/400 Toolkit for Java. You'll find the tools and documentation for using data queues in Java there.

  • RELEVANCY SCORE 3.04

    DB:3.04:Pro*Cobol Precompiler ps


    Hi!

    I am intending to learn how to use an application write in COBOL work thruout the Oracle and then I downloaded Oracle 9i database (9.2.0.1.0) and I installed it on my PC. When I used the sample code file named "sample1" and I executed it by the .bat "makeit", where there is a component called "cobol", I saw that this component is not in anywhere of my PC and, naturally, my sample1 did not work. Could anyone please tell me where I find the cobol component to download it?

    Thankful.

    DB:3.04:Pro*Cobol Precompiler ps

    There are some things that are automatically included. Others need to be included manually.

    Apparently the Precompiler Common Files are included in the default install. But the Precompilers are part of the Programmer kit and do not seem to be included by default.

  • RELEVANCY SCORE 3.03

    DB:3.03:Pessimistic Locking (Relating To Cobol) zx


    Hi,

    Apologies for the SA I've written below - just wanted to explain the context around my problem.

    I'm working on an application which replaces the Micro Focus COBOL file handler allows data in COBOL VSAM files to be migrated to Oracle in such a way that the COBOL source code doesn't have to change.

    The last problem we're having is in replicating COBOL's pessimistic locking paradigm in that a COBOL READ with LOCK statement will take a lock on the row that's read, and won't release the lock until an explicit UNLOCK statement is issued.

    Each IO command from COBOL ends up calling an Oracle procedure, so what I'm after is ideas on how to create a procedure which when called will select one record create a row lock, and hold that lock until another stored procedure call (to the unlock) procedure is made.

    Using Select ... for update will work provided we're in a database transaction, however that causes other headaches because currently we're sharing one database connection across all files that are opened by a running COBOL program, the files need to be locked unlocked independently from each other.

    If that's the only way to achieve the lock I can work with that by changing our application to create a connection for a file when it needs to lock a record, but does anyone have any out of the box ideas?

    thanks, Darren.

    DB:3.03:Pessimistic Locking (Relating To Cobol) zx

    This is not an easy problem to solve due to a very big difference between file (ISAM) based locking and RDBMS transactions.

    A lock in a RBMS is not just a "mere row lock" - it is part of a transaction. And a lock cannot span a transaction. To emulate file-based locking in any RDBMS will be problematic as a result.

    It can be done in Oracle. Heck, there is little one cannot do in Oracle. However, some designs (like this file-based record locking) simply does not scale.

    And precisely for that reason, Oracle does not have a Lock Manager. There is no special monolithic structure (memory or table) that contains a list of locks. Any new lock, any release of an existing lock, will require access to that structure - and serialised access. This means it will become a huge bottleneck the more locks there are and the more processes wants locks. And this is the reason why there are lock escalation problems in SQL-Server, why locks are "expensive". Why the Ingres RDBMS manual goes into great lengths of how to "tune" the database for this, to the effect of having to decide whether to boost OLTP processing or read-only queries - as you cannot run both as effectively as you want.

    In order for you to emulate the file-lock approach, this is exactly what you will need to simulate in Oracle. A monolithic lock manager.

    Not that difficult to design and implement in Oracle. Pessimistic locking in Oracle is essentially "turned off" and you manage application row locking via your own PL/SQL lock manager in Oracle. Using autonomous transactions extensively.

    But this will not scale. Sure, it can handle maybe 200 users. Maybe more. But as the userbase increases, so the system will slow down - as you have no choice but to enforce serialisation in your PL/SQL lock manager to handling locking.

    There is a price to pay for not wanting to change the Cobol code to correctly use Oracle's concurrency model.

    Personally, I would argue long and very hard that this price is unacceptable and that none of the ROI in an "expensive" RDBMS is realised. Any RDBMS makes a very poor ISAM file system. So why bother?

  • RELEVANCY SCORE 3.00

    DB:3.00:Return Ref Cursor From Database Link/Stored Proc? Do-Able? 7m


    Is it possible to return a REF CURSOR from a stored procedure that is being called from a remote database via a database link???

    We are trying from Pro*Cobol on MVS (which has db link pointing to AIX thru db link) and get a 00993 error, which seems to say this is not possible.

    Before I give up, thought I would check with the experts....

    Thanks in advance.

    DB:3.00:Return Ref Cursor From Database Link/Stored Proc? Do-Able? 7m

    Is it possible to return a REF CURSOR from a stored procedure that is being called from a remote database via a database link???

    We are trying from Pro*Cobol on MVS (which has db link pointing to AIX thru db link) and get a 00993 error, which seems to say this is not possible.

    Before I give up, thought I would check with the experts....

    Thanks in advance.

  • RELEVANCY SCORE 2.98

    DB:2.98:Creating A Cobol Service za


    Hi,

    I need to customize a base COBOL Service. With the COBOL Source file CIPxxxxx i can add my custom logic but how to convert my CMPxxxxx COBOL Program to CMLxxxxx COBOL Service ? As per my understanding we need to convert a COBOL Program to a COBOL service to use it in inbound Service. Suggestions please

    DB:2.98:Creating A Cobol Service za

    Hi,

    I need to customize a base COBOL Service. With the COBOL Source file CIPxxxxx i can add my custom logic but how to convert my CMPxxxxx COBOL Program to CMLxxxxx COBOL Service ? As per my understanding we need to convert a COBOL Program to a COBOL service to use it in inbound Service. Suggestions please

  • RELEVANCY SCORE 2.98

    DB:2.98:Tuxedo Compatibility With Mf Cobol 11


    Hi,

    I would like to know the version of Tuxedo(6.5 or later) which will be compatible with Micro Focus Cobol v5.1 on AIX 6 and Oracle 10g. Currently we are running Tuxedo 6.5 on AIX 5, also please advise if we can continue using the same version of Tuxedo on AIX 6.
    Could somebody help me on this?

    DB:2.98:Tuxedo Compatibility With Mf Cobol 11

    Hi,

    You need to look at the Platform Data Sheets for the version you are interested in. A quick glance at the oldest version of Tuxedo that is still available with standard support which is Tuxedo 9.0 (http://download.oracle.com/docs/cd/E13203_01/tuxedo/tux90/install/inspds.htm), indicates that MF COBOL Server Express 4.0sp1 or later is supported. You can continue on the same version of Tuxedo, but only if you purchase extended support as standard support is no longer available for Tuxedo 6.5 on AIX.

    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • RELEVANCY SCORE 2.98

    DB:2.98:Connectivity Of Hp Cobol Apps On Openvms Alpha,Openvms I64,Openvms Os To Db 8a


    How to connect Oracle Database to applications built upon HP COBOL deployed on the OpenVMS Alpha, OpenVMS I64 and OpenVMS VAX operating systems.

    Also, currently the customer is using flat file system for data handling and according to the prodcut documentation:
    "With HP COBOL, Oracle CODYSAL DBMS database programs can be used for the connectivity to Oracle DBMS. "

    Need help to know how to establish this connectivity and what added components be used for such situation.

    Thank you

    Regards,
    Murad

    DB:2.98:Connectivity Of Hp Cobol Apps On Openvms Alpha,Openvms I64,Openvms Os To Db 8a

    How to connect Oracle Database to applications built upon HP COBOL deployed on the OpenVMS Alpha, OpenVMS I64 and OpenVMS VAX operating systems.

    Also, currently the customer is using flat file system for data handling and according to the prodcut documentation:
    "With HP COBOL, Oracle CODYSAL DBMS database programs can be used for the connectivity to Oracle DBMS. "

    Need help to know how to establish this connectivity and what added components be used for such situation.

    Thank you

    Regards,
    Murad

  • RELEVANCY SCORE 2.98

    DB:2.98:Pro*Cobol Compilation Problems 3j


    I have an Oracle8I DB installed on a Unix CompaqTru64 machine. I have Cobol Programs installed on the same machine(Micro Focus Cobol). When I tried to compile the Cobol Programs using the Pro*Cobol Precompiler installed on the server as an Oracle utility ,an error is issued :
    "/usr/bin/cob : library not found : -lsgr"
    and the compilation can't be done.
    "/usr/bin/cob " is the Cobol Compiler Name as specified in the Cobol makefile.
    Can someone help me, please?
    Thanks.

    DB:2.98:Pro*Cobol Compilation Problems 3j

    I have an Oracle8I DB installed on a Unix CompaqTru64 machine. I have Cobol Programs installed on the same machine(Micro Focus Cobol). When I tried to compile the Cobol Programs using the Pro*Cobol Precompiler installed on the server as an Oracle utility ,an error is issued :
    "/usr/bin/cob : library not found : -lsgr"
    and the compilation can't be done.
    "/usr/bin/cob " is the Cobol Compiler Name as specified in the Cobol makefile.
    Can someone help me, please?
    Thanks.

  • RELEVANCY SCORE 2.97

    DB:2.97:Cobol Pro*Compiler On Linux s9


    Hello,
    Is the Cobol Pro*compiler is available on Linux ?

    DB:2.97:Cobol Pro*Compiler On Linux s9

    Hello,
    Is the Cobol Pro*compiler is available on Linux ?

  • RELEVANCY SCORE 2.96

    DB:2.96:Pro*Cobol And Dbms_Output.Put_Line jm


    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?

    DB:2.96:Pro*Cobol And Dbms_Output.Put_Line jm

    '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

  • RELEVANCY SCORE 2.95

    DB:2.95:Error In Buildserver For Ibm Cobol - Db2 Program With Atmi Calls ck


    Hi..

    Am using IBM COBOL for AIX version 5.3..
    I have installed Oracle Tuxedo 10g R3 on AIX and IBM DB2 V9.5 on AIX..

    I have written a sample Cobol-DB2 program with ATMI calls for client and server..
    I have precompiled the programs with the command..
    db2 prep COBDBCL.sqb bindfile target ibmcob CALL_RESOLUTION DEFERRED and
    db2 prep COBDBSR.sqb bindfile target ibmcob CALL_RESOLUTION DEFERRED

    and for binding
    db2 bind COBDBCL.bnd and
    db2 bind COBDBSR.bnd

    and for compiling the generated .cbl files i have used this command.
    cob2 -qpgmname\(mixed\) -qlib -I$DB2PATH/include/cobol_a -c COBDBCL.cbl
    cob2 -qpgmname\(mixed\) -qlib -I$DB2PATH/include/cobol_a -c COBDBSR.cbl

    and for building the client and server
    buildclient -C -o COBDBCL -f COBDBCL.cbl and
    buildserver -C -o COBDBSR -s COBDBSR -f COBDBSR.cbl

    Here buildclient is working fine since there is no copy book for "SQLCA" here. but for buildserver am getting this errors..
    PP 5724-H44 IBM COBOL for AIX 2.0.0 in progress ...
    LineID Message code Library phase message text
    280 IGYLI0049-S The "COPY" library was not found. Skipped to the period
    terminating the "COPY" statement.
    Messages Total Informational Warning Error Severe Terminating
    Printed: 1 1
    LineID Message code Message text
    IGYSC0185-I Messages were issued during library phase processing.
    Refer to the beginning of the listing.
    325 IGYPS2121-S "SQLCA" was not defined as a data-name. The statement
    was discarded.
    Same message on line: 332 408 431 501 514
    590 600 618
    Messages Total Informational Warning Error Severe Terminating
    Printed: 10 1 9
    End of compilation 1, program COBDBSR, highest severity: Severe.
    Return code 12
    CMDTUX_CAT:1839: ERROR: can't execute cob2 -c -I/usr/Oracle/Tuxedo10g/cobinclude COBDBSR.cbl

    I have included the library path of DB2 in LIBPATH and path od DB2 in PATH environment variable..

    Am i missing any option while building?? whether the steps which i followed are correct??

    Need ur help..

    Thanks in advance..

    DB:2.95:Error In Buildserver For Ibm Cobol - Db2 Program With Atmi Calls ck

    Hi Todd,

    Thanks for ur reply.. I have given the wrong path for DB2 library.. Now i have corrected it and buildtms is working fine..

    ${DB2DIR}/lib is the correct one and DB2DIR is the path of the sqllib under the DB2 instance..

  • RELEVANCY SCORE 2.94

    DB:2.94:Re: Using With Clause In Pro*Cobol 9k


    Could you create a permanent view DPTCOST instead of 'with DPTCOST' ?
    or could you apply dynamic sql ?

    Some client tools might support new feature on SQL, plsql etc. behind Server(RDBMS engine).

    DB:2.94:Re: Using With Clause In Pro*Cobol 9k

    I am taking the work left by the prev programmer who stated putting the query into temp table will increase the performance.
    I use MV instead to simplify the program.

    The main query has about 28161 rows returned, and there are 2 more queries executed for each of them.
    From my opinion the individuals queries are the actual bottle neck, however refactoring them requires me to modify the COBOL structure, which I want to avoid.

    Sometimes idealist is not working in this capitalist corporation.

  • RELEVANCY SCORE 2.94

    DB:2.94:Pro*Cobol On Vms 37


    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

    DB:2.94:Pro*Cobol On Vms 37

    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

  • RELEVANCY SCORE 2.93

    DB:2.93:What Is The Future For Cobol User Exits? pm


    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

    DB:2.93:What Is The Future For Cobol User Exits? pm

    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

  • RELEVANCY SCORE 2.93

    DB:2.93:Pro*Cobol Is Missing In 10g For Win64 j3


    Hi !

    The quesion is for Oracle people.
    Pro*Cobol is missing in 10g for win64.

    Any chances to get it ?

    As a matter of fact if you precompile on HPUX (64-bit) even on 9i and edit the produced code, you can make your program work.

    Regards,
    Sergey

    DB:2.93:Pro*Cobol Is Missing In 10g For Win64 j3

    Hi !

    The quesion is for Oracle people.
    Pro*Cobol is missing in 10g for win64.

    Any chances to get it ?

    As a matter of fact if you precompile on HPUX (64-bit) even on 9i and edit the produced code, you can make your program work.

    Regards,
    Sergey

  • RELEVANCY SCORE 2.91

    DB:2.91:Pro * Cobol With Oracle 9i mx


    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.

    DB:2.91:Pro * Cobol With Oracle 9i mx

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

  • RELEVANCY SCORE 2.89

    DB:2.89:Does Oracle Intent To Maintain The Pro*Cobol In The Market? 71


    With the new power languages like java, the Pro*Cobol segment will survive in news releases?

    DB:2.89:Does Oracle Intent To Maintain The Pro*Cobol In The Market? 71

    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

  • RELEVANCY SCORE 2.87

    DB:2.87:Cobol Wrapper To Atmos Rest Api z7



    One of our prospects is looking for examples of storing and retrieving ATMOS objects from a homegrown COBOL application.

    Is there a COBOL wrapper example that anyone can share with me or are there alternative methods that are used for COBOL (like calling a java function in COBOL). Anyone developed a COBOL integration with EMC ATMOS?

    Robert

    EMC EMEA Executive Briefing Center

    DB:2.87:Cobol Wrapper To Atmos Rest Api z7

    Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.

    You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "Atmos Support Forum"

    Atmos Support Forum

    Seeing though that over 7 months have elapsed since you posted, maybe you have already found the answer (possibly opened up a ticket with support)? If so, once relocated, consider sharing the resolution and also marking the question as "Answered" so that it can help others that have the same question. If not, once relocated, it will then have more visibility by the community of dedicated customers, partners, and EMC employees that are eager to assist.

  • RELEVANCY SCORE 2.87

    DB:2.87:Pro*Cobol In Oracle 10g k1


    Hi all,
    I don't find precompiler procob in $ORACLE_HOME/bin. I have installed Enterprise Edition 10g on Solaris10. Please help me, thanks.

    DB:2.87:Pro*Cobol In Oracle 10g k1

    It is not installed by default, you'll have to perform a custom installation and explicitly select it.

  • RELEVANCY SCORE 2.86

    DB:2.86:Pro*Cobol Oracle 9.2 77


    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?

    DB:2.86:Pro*Cobol Oracle 9.2 77

    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?

  • RELEVANCY SCORE 2.85

    DB:2.85:Re: Problems With Archive On 10g!! Need Restart Database Always!! pa


    This thread might help

    oracle 10g flashback error

    DB:2.85:Re: Problems With Archive On 10g!! Need Restart Database Always!! pa

    Paulo,

    How did you fix the access to asmcmd. I can't acces and I have tried everything.

    Thanks,

    Terry

  • RELEVANCY SCORE 2.83

    DB:2.83:Oracle 10g 32b Client For Hp-Ux Risc 7a


    Is there 32b client for Oracle 10g r2 for HP-UX RISC? Where can we download it as we cant find the link?

    We are planning to install our target application is 32b and Oracle 10g R2 in one server, HP UX-RISC (HP-UX 11i v2) . Our plan is to have an Oracle 10g 64b server, a 32b app and a 32b microfocus cobol software all on the same box. it is our understanding that to compile the cobol software as 32b we need the Oracle 10g 32b client...

    Your help is very much appreciated...

    DB:2.83:Oracle 10g 32b Client For Hp-Ux Risc 7a

    ldelrosa@altera.com wrote:
    Another option for us is to use Sun solaris. We are aware that there is 32b client version for Windows and Linux for Oracle 10g. Are there any 32b client for Oracle 10g for HP-UX RISC or Sun Solaris?I just have noticed this as I was passing and I haven't really got time to investigate.

    1) What you may be looking for is 32bit client libraries which may well be included in a 64 bit distribution, rather than for an actual 32 bit client.

    2) If you really wanted a 32 bit on sun solaris 10 an option might be to run a whole root zone ... this is really a random thought going through my head. I would have to spend time checking ths out and I dont have at present.

    This is a brainstorm reply with a lot of thought being given to it. I believe the first suggestion may have some value.

    RGds -bigdelboy.

    Edited by: bigdelboy on 08-Nov-2009 01:57 (hmm this is proably a prodcut related question which should really be on another forum)

  • RELEVANCY SCORE 2.81

    DB:2.81:Oracle 8.0.5 Pro*Cobol For Hp-Ux 11.0 xp


    --
    The Oracle8 Administrator's Reference, release 8.0.5 for HP9000
    servers states "Pro*COBOL is not available for 64-bit HP-UX 11.0
    systems." Any idea why? Are there any plans to support it in
    the future (the sooner the better)?

    We currenly have 2 systems that use MicroFocus COBOL and Oracle
    7.3.x Pro*COBOL pre-compilers.

    We are considering moving to a 64-bit HP loaded with HP-UX 11.0
    and Oracle8. If Oracle doesn't support/has no intention of
    supporting Pro*COBOL on this platform, we need to know before we
    make the move.

    Thank you.
    null

    DB:2.81:Oracle 8.0.5 Pro*Cobol For Hp-Ux 11.0 xp

    --
    Hi Christina,

    Unfortunately, I do not know the answer to your question. I would
    recommend that you contact Oracle Support (precompilers section)
    directly for this information.

    Our group is mainly concerned with migrating non-Oracle databases
    and applications to Oracle and as such we do not have a lot of
    information on Oracle Precompilers future directions.

    Regards

    John

    Christina Wilson (guest) wrote:
    : The Oracle8 Administrator's Reference, release 8.0.5 for HP9000
    : servers states "Pro*COBOL is not available for 64-bit HP-UX
    11.0
    : systems." Any idea why? Are there any plans to support it in
    : the future (the sooner the better)?
    : We currenly have 2 systems that use MicroFocus COBOL and Oracle
    : 7.3.x Pro*COBOL pre-compilers.
    : We are considering moving to a 64-bit HP loaded with HP-UX 11.0
    : and Oracle8. If Oracle doesn't support/has no intention of
    : supporting Pro*COBOL on this platform, we need to know before
    we
    : make the move.
    : Thank you.

    _________________________
    Oracle Technology Network
    http://technet.oracle.com
    null

  • RELEVANCY SCORE 2.80

    DB:2.80:Is Our Server Identical? p3


    Hi Friendz,

    We have two Identical servers DEV1 and PROD1 with same SunOS and Oracle Db versions.

    Then we have a pro*cobol program "prog1" which compile clean at DEV1, but when copied to PROD1 and compiled it does not
    go clean compile.

    Can you help me how to troubleshoot this problem please.

    Is there a bug in Oracle pro*cobol that I may not be aware of?

    How do I compare the pro*cobol version of the 2 servers?

    I also tried to check the server OS versions:

    @DEV1

    uname -a

    SunOS DEV1 5.10 Generic_144488-12 sun4v sparc SUNW,T5440

    @PROD1

    uname -a

    SunOS PROD1 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Fire-V440Are our OS in sync?

    MF cobol version:

    check cobrun:

    DEV1 MF Cobol Version:
    V5.1 revision 0 build 10/10/2 G; 07109. Run Time System RXCTI/AA0/00000Q.

    DEV2 MF Cobol Version:
    V5.1 revision 0 build 10/10/2 G; 07209. Run Time System RXCTI/AA0/00000QIs our cobol compiler in sync?

    Thanks a lot,

    DB:2.80:Is Our Server Identical? p3

    Well, first of all, the CPUs on your two systems are very different. One is of sun4v architecture whereas the other is sun4u. Whether you can move the compiled binaries for your pro*cobol depends on whether the compiler explicitly generates code for a specific CPU type only or generates more generic codes. There may be a compile option flag to change what type of CPUs the compiled code will run on.

  • RELEVANCY SCORE 2.80

    DB:2.80:Compile Sample Procobol Program On Linux 64 Bit 7f


    I am trying to compile and run a procobol sample program on a linux 64 bit machine.

    When I try to compile with the demo makefile I get

    ld: skipping incompatible /home/oracle/10G/lib//libclntsh.so when searching for -lclntsh

    So i have added LIBDIR=lib32 to my make command

    make LIBDIR=lib32 -f demo_procob.mk sample1

    And it now compiles but when I run it I get

    Execution error : file 'sample1'
    error code: 114, pc=0, call=1, seg=0
    114 Attempt to access item beyond bounds of memory (Signal 11)

    This happens when it is trying to connect.

    FYI I have tried it with export COBMODE=32
    and
    echo $LD_LIBRARY_PATH gives

    /home/oracle/10G/lib32:/home/oracle/10G/lib::/usr/local/jdk/jre/lib/amd64:/opt/microfocus/cobol/lib

    Would be gratefull for any help on what I suspect is a 32/64 bit issue.

    Steve

    DB:2.80:Compile Sample Procobol Program On Linux 64 Bit 7f

    I have encountred the same problem, the solution for this is to execute relink all libraries:

    $relink all

    Good luck
    Hedi LABIDI

  • RELEVANCY SCORE 2.80

    DB:2.80:Pro*Cobol, Linux &Amp; Oracle 9i pk


    There is an old Oracle 7.3.4-based application on a very old Unix. The application is written in Cobol and evidently used Oracle's Pro*Cobol precompiler product.

    Now, we're porting to Oracle 9i, possibly powered by Linux. I can't find Pro*Cobol for anything past Oracle 8. Was Pro*Cobol functionally replaced by something else? Is that (or its equivalent) still needed? Thanks in advance.

    (My email is patk@conservor.com)

    DB:2.80:Pro*Cobol, Linux &Amp; Oracle 9i pk

    There is an old Oracle 7.3.4-based application on a very old Unix. The application is written in Cobol and evidently used Oracle's Pro*Cobol precompiler product.

    Now, we're porting to Oracle 9i, possibly powered by Linux. I can't find Pro*Cobol for anything past Oracle 8. Was Pro*Cobol functionally replaced by something else? Is that (or its equivalent) still needed? Thanks in advance.

    (My email is patk@conservor.com)

  • RELEVANCY SCORE 2.79

    DB:2.79:Upgrading Oracle 8.0.6 And Forms 5.0.6.8.0, Reports 3.0.5.8.0, Pro*C/Cobol zf


    Hi,

    We are researching upgrading to 10g(10.1) for database and Developer tools. The database is currently 8.0.6 and we use Oracle Forms 5.0.6.8.0; Oracle Reports 3.0.5.8.0; and precompile Pro*C/COBOL programs with the 8.0.4.4 environment. There appears to be quite a bit of information on the database upgrade. I am looking for Forms and Reports data as well as Pro*C and Pro*COBOL. The platform is currently AIX 4.3.3 ML11 and we will be upgrading to AIX 5.2.5 prior to the database upgrade. Would someone be able to point me to some reference materials? Are there any land mines I should be concerned with? Is this possible? Would going to 6i or 9i for Developer be an option if 10g is not?

    Thanks!

    DB:2.79:Upgrading Oracle 8.0.6 And Forms 5.0.6.8.0, Reports 3.0.5.8.0, Pro*C/Cobol zf

    Migrating Forms to the web:
    http://www.oracle.com/technology/products/forms/pdf/forms9icstowebmigration.pdf

    There are so many other related documents on OTN. Just go to
    http://www.oracle.com/technology/products/ids/index.html

  • RELEVANCY SCORE 2.79

    DB:2.79:Pro*Cobol Pre-Compiler Does Not Recognize Sql Functions 1z


    Greetings to all,

    I have been using the Pro*Cobol pre-compiler with embedded SQL just a few weeks. I am trying to include a CASE statement with a SQL string function as one of the returned values of a SELECT statement, but the pre-compiler rejects such a statement. It works just right with SQL*Plus.

    e.g. SELECT a, b,
    CASE
    WHEN (SUBSTR(a,1,3) 'abc') THEN 'xyz'
    ELSE 'zyx'
    END c,
    d
    FROM e;

    I would appreciate any help or ideas about the Pro*Cobol configuration.

    Thanks,

    Dan

    DB:2.79:Pro*Cobol Pre-Compiler Does Not Recognize Sql Functions 1z

    Hi Kamal,

    In response to your questions:

    1. Using Pro*Cobol version 10.1.0.2.0 against
    2. ORACLE 10g database.

    I've been told NOT to use views in this environment.
    I was wondering whether changing the SQLCHECK option value to SEMANTIC or FULL might help.

    Thanks,

    Dan

  • RELEVANCY SCORE 2.78

    DB:2.78:Initiating An Openvms Session From Forms 5.0 zs


    --
    I'm currently converting a SQL*Forms 3.0 application running on
    a DEC OpenVMS server to a Forms 5.0 application running on
    Windows NT. The current system runs a COM script file that
    displays a SQL*Forms screen by issuing a RUNFORM command. When
    the user exits the screen, a Pro*COBOL program is initiated by
    issuing a SUBMIT command. Lastly, when the COBOL program
    finishes, a PL/SQL script is run by initiating SQL*Plus.
    I'm trying to determine how I can initiate an OpenVMS session
    from Forms 5.0. FFI and User Exits only appear to work with
    Pro*C module (unfortunately we have no C experience).
    Does Oracle or any other vendor have a product, utility, or
    method for connecting to OpenVMS from Windows NT Forms 5.0
    module??
    Any help would be welcome. Thanks!!
    null

    DB:2.78:Initiating An Openvms Session From Forms 5.0 zs

    --
    I'm currently converting a SQL*Forms 3.0 application running on
    a DEC OpenVMS server to a Forms 5.0 application running on
    Windows NT. The current system runs a COM script file that
    displays a SQL*Forms screen by issuing a RUNFORM command. When
    the user exits the screen, a Pro*COBOL program is initiated by
    issuing a SUBMIT command. Lastly, when the COBOL program
    finishes, a PL/SQL script is run by initiating SQL*Plus.
    I'm trying to determine how I can initiate an OpenVMS session
    from Forms 5.0. FFI and User Exits only appear to work with
    Pro*C module (unfortunately we have no C experience).
    Does Oracle or any other vendor have a product, utility, or
    method for connecting to OpenVMS from Windows NT Forms 5.0
    module??
    Any help would be welcome. Thanks!!
    null

  • RELEVANCY SCORE 2.78

    DB:2.78:Unable To Use Output Keyword When Calling Stored Procedure In Procobol m3


    I am porting COBOL code from sybase to Oracle compiling with the Oracle Pro*Cobol Precompiler using NetExpress 5.1 and getting COBCH0149S No SQL directives have been set when passing 'output' in stored procedure calls. Any suggestions on how to get this to work?

    EXEC SQL
    EXEC CO_GET_DATE
    : HOST-VARIABLES.H-CURRENT-DATE OUTPUT
    END-EXEC.

    I had to change EXEC to CALL
    if i remove 'OUTPUT' it compiles but i need to pass OUTPUT to the stored procedure

    EXEC SQL
    CALL CO_GET_DATE
    : HOST-VARIABLES.H-CURRENT-DATE
    END-EXEC.

    Here are my project options
    %FILENAME COBIDY(%TARGETDIR) WB3 WB CSI ANIM EDITOR(MF2) ENSUITE(3) QUAL NOGNT INT(%TARGETDIR\%BASENAME.int) MAKESYN "COMP-5" = "COMP" p(COBSQL) COBSQLTYPE=ORACLE8 preprocess"cp" ENDp;

    DB:2.78:Unable To Use Output Keyword When Calling Stored Procedure In Procobol m3

    I am porting COBOL code from sybase to Oracle compiling with the Oracle Pro*Cobol Precompiler using NetExpress 5.1 and getting COBCH0149S No SQL directives have been set when passing 'output' in stored procedure calls. Any suggestions on how to get this to work?

    EXEC SQL
    EXEC CO_GET_DATE
    : HOST-VARIABLES.H-CURRENT-DATE OUTPUT
    END-EXEC.

    I had to change EXEC to CALL
    if i remove 'OUTPUT' it compiles but i need to pass OUTPUT to the stored procedure

    EXEC SQL
    CALL CO_GET_DATE
    : HOST-VARIABLES.H-CURRENT-DATE
    END-EXEC.

    Here are my project options
    %FILENAME COBIDY(%TARGETDIR) WB3 WB CSI ANIM EDITOR(MF2) ENSUITE(3) QUAL NOGNT INT(%TARGETDIR\%BASENAME.int) MAKESYN "COMP-5" = "COMP" p(COBSQL) COBSQLTYPE=ORACLE8 preprocess"cp" ENDp;

  • RELEVANCY SCORE 2.78

    DB:2.78:Forms 6i Calling Pro*Cobol 8i User-Exits On Nt jk


    Hello.

    At runtime, all our Forms 6i programs CRASHED when calling PRO*COBOL 8i user-exits that reside on f60xtb.dll. The PRO*COBOL programs were precompiled using the PRO*COBOL compiler that goes with Oracle 8i client CD for NT.

    I think the solution is to pre-compile all the PRO*COBOL programs using Oracle 8.0(Oracle 8.0.5. or Oracle 8.0.6)PRO*COBOL precompiler which goes with Oracle 8 client CD before creating the f60xtb.dll. I think Forms6i is NOT compatible with Oracle 8i PRO*COBOL compiler.

    Please advise. Thank you.

    Regards,
    Armando Abeleda
    Lynx Financial Systems, Australia

    null

    DB:2.78:Forms 6i Calling Pro*Cobol 8i User-Exits On Nt jk

    Hello.

    At runtime, all our Forms 6i programs CRASHED when calling PRO*COBOL 8i user-exits that reside on f60xtb.dll. The PRO*COBOL programs were precompiled using the PRO*COBOL compiler that goes with Oracle 8i client CD for NT.

    I think the solution is to pre-compile all the PRO*COBOL programs using Oracle 8.0(Oracle 8.0.5. or Oracle 8.0.6)PRO*COBOL precompiler which goes with Oracle 8 client CD before creating the f60xtb.dll. I think Forms6i is NOT compatible with Oracle 8i PRO*COBOL compiler.

    Please advise. Thank you.

    Regards,
    Armando Abeleda
    Lynx Financial Systems, Australia

    null

  • RELEVANCY SCORE 2.76

    DB:2.76:Unable To Locate The Pro Cobol Compiler 1a


    I'm installed Oracle 9i client using Oracle 9.2.0.2.0 for HP-UX.
    The Pro Cobol compiler is not present in any of the installation options.

    Where can I download Oracle Pro Cobol compiler for Oracle 9.2.0.2.0 for HP-UX?

    G-

    DB:2.76:Unable To Locate The Pro Cobol Compiler 1a

    after some research I found out that the Pro Cobol compiler is not available on the HP Itanium for version 9.2.0.1, 9.2.0.2 and 9.2.0.3. I will not be available until 9.2.0.4 or later per Oracle on Metalink

  • RELEVANCY SCORE 2.75

    DB:2.75:How To Call A Cobol Function From Java? 7m


    Hi all,
    I have a Cobol application running on a Linux machine. The application takes in certain inputs from the user (from the Linux command prompt) and stores them within text files in its local directory. Again when the user enters a search keyword the Cobol looksup these files and retrieves the related information on a successful search. I dont have access to the text files but I have access to the application (I have the whole Cobol application coding available with me).

    My task is to develop a Java program that would interface with this Cobol application, call the Cobol functions that do the input/output with the text files and trap the necessary output.

    Can anybody suggest how to go about this. Had the coding been in C/C++ I would have thought of usingt Java Native Interface, but how to do it for Cobol?

    Thanks in advance.

    I am posting this everywhere to get attention. Sorry for the multiple posting.
    snodx

    DB:2.75:How To Call A Cobol Function From Java? 7m

    Don't apologize for cross-posting, just don't do it. Enough attention for you?

  • RELEVANCY SCORE 2.75

    DB:2.75:For Cobol!! 77


     
    HEY FOR THOSE STUDENTS WHO ARE NEW TO PROGRAMING LANGUAGES....
    SPECIALY WHO GETS TROUBLE WITH COBOL(like me)
     
    YOU CAN GET VERY USEFULL STUFF FROM THESE SITES!!!!(as i did )
     
    http://www.csis.ul.ie/COBOL/
    http://www.lacitec.on.ca/~jlemoe/Cobol/Materiel/Cobol/Manuel/index.htm

  • RELEVANCY SCORE 2.75

    DB:2.75:Pro*Cobol xm


    We have a Cobol application written in Micro Focus COBOL that uses Pro*COBOL (on Windows). Can this application work with instant client? Or must a "regular" client install be done on the boxes that would use it?

    Thank you.

    DB:2.75:Pro*Cobol xm

    We have a Cobol application written in Micro Focus COBOL that uses Pro*COBOL (on Windows). Can this application work with instant client? Or must a "regular" client install be done on the boxes that would use it?

    Thank you.

  • RELEVANCY SCORE 2.74

    DB:2.74:Call From Cobol Program On Os 390 pj


    DB:2.74:Call From Cobol Program On Os 390 pj

    Don Ferguson don@bea.com writes:

    What does IBM offer in this space? I guess its possible to envisage
    calling an EJB from a COBOL program over IIOP, but no-one has tried
    it. If this is how IBM does it then it should work with us also under 6.1

    andy

    Roman wrote:

    Hi .

    Try to WLS6 and WTC -- weblogic tuxedo connector and Elink 4 for connectivity
    between OS390 CICS and Tuxedo.
    IBM Websphere offers more as for EJB - OS390 system. But Weblogic is better
    J2EE server (global view), in my opinion.

    Roman

    "Cameron Purdy" cpurdy@tangosol.com wrote:
    I'd suggest CORBA (2.3 or later).

    --
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com
    +1.617.623.5782
    WebLogic Consulting Available

    "Marc Lenart" lenart17@rcn.com wrote in message
    news:3a8956f2$1@newsgroups.bea.com...
    Can you steer me in the right direction as to how I can call a sessionbean from a
    cobol program on the OS390 platform? An example wouyld be helpful.Thank
    You!
    --

  • RELEVANCY SCORE 2.74

    DB:2.74:Pro*Cobol Compilation Error 31


    Hi all,

    We have two Identical servers DEV1 and PROD1 with same SunOS and Oracle Db versions.

    Then we have a pro*cobol program "prog1" which compile clean at DEV1, but when copied to PROD1 and compiled it does not
    go clean compile.

    Can you help me how to troubleshoot this problem please.

    Is there a bug in Oracle pro*cobol that I may not be aware of?

    How do I compare the pro*cobol version of the 2 servers?

    I also tried to check the server OS versions:

    @DEV1

    uname -a

    SunOS DEV1 5.10 Generic_144488-12 sun4v sparc SUNW,T5440

    @PROD1

    uname -a

    SunOS PROD1 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Fire-V440Are our OS in sync?

    MF cobol version:

    check cobrun:

    DEV1 MF Cobol Version:
    V5.1 revision 0 build 10/10/2 G; 07109. Run Time System RXCTI/AA0/00000Q.

    DEV2 MF Cobol Version:
    V5.1 revision 0 build 10/10/2 G; 07209. Run Time System RXCTI/AA0/00000QIs our cobol compiler in sync?

    Thanks a lot,

    Edited by: KinsaKaUy? on 16-Sep-2011 02:44

    DB:2.74:Pro*Cobol Compilation Error 31

    What kind of error it throw ??
    Are both server have similar hardware configuration??

    Thanks
    Cheeta

  • RELEVANCY SCORE 2.74

    DB:2.74:Pro*Cobol Pco Compilation Problem In Linux 79


    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..

    DB:2.74:Pro*Cobol Pco Compilation Problem In Linux 79

    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

  • RELEVANCY SCORE 2.73

    DB:2.73:Pro*Cobol For 9i When ? k8


    I'd like to know if and when Pro*Cobol will be released on 9i Database.
    TIA
    Tullio

    DB:2.73:Pro*Cobol For 9i When ? k8

    I'd like to know if and when Pro*Cobol will be released on 9i Database.
    TIA
    Tullio

  • RELEVANCY SCORE 2.73

    DB:2.73:Re: Calling Cobol From Forte d9


    Hi,

    I am intimately familiear with how Forte interfaces with COBOL. In my
    situation we took legacy COBOL and moved it to HP-UX Server running
    Micro Focus COBOL. The Micro Focus COBOL runtime does accomodate a
    C-Callin.
    Therefore standard Forte wrappers were built to call the COBOL routine
    directly. COBOL procedures appear to Forte as C functions.

    You may need to add a layer of C code in front of the COBOL, but it will
    depend on how the COBOL code is structured.

    There were issues related to the run-time libraries of COBOL which by
    now I believe to have been simplified. If you want to discuss details,
    I'd be glad to explain in more detail based on the specifics of your
    situation.

    Regards,
    jim

    Digital/Forte 06-Feb-1997 1512 wrote:

    The only way I am aware of calling COBOL programs from Forte is through
    C-wrappering since Forte does not provide a direct interface to COBOL.
    This has been done on various platforms but with complex data structures
    this can be turn out to be messy.

    There are a lot of other middleware supported by Forte like
    ObjectBrokerDCE but COBOL is not supported directly by these products either.

    I am not aware of what kind of processing your COBOL and Forte apps
    do (interactive/batch) or what databases (if any) are involved,but it may be
    easier for both to interact with a common database if it is feasible.

    Does anyone else have better ideas?

    - Arvind
    --
    Jim Rice mailto:jim@forte.com
    Forte Software, Inc. http://www.forte.com
    Tech Sales Mgr, Eastern Div.
    703-749-1445 Fax# 749-1447 Corp: 510-869-3400 x2316

    DB:2.73:Re: Calling Cobol From Forte d9

    To: forte-users@Sagesoln.com
    cc:
    Subject: Calling COBOL from Forte

    We have a large complex COBOL program that we've purchased that we
    currently run on our mainframe system. We are in the process of re-writing
    our system into FORTE but we want to keep this COBOL program. This COBOL
    program would need to be called from FORTE and it in turn would need to
    call FORTE methods. The interface between FORTE and COBOL would be done by
    passing large data structures as parameters containing both Character and
    Integer data fields. Can this be done since I'm not looking forward to
    having to re-write this entire program in FORTE?

    ----------------------------------------------
    David Wilbur email: dwilbur@uwindsor.ca
    University of Windsor phone: 519-253-4232 ext. 2779
    Windsor, Ontario Canada
    -----------------------------------------------

  • RELEVANCY SCORE 2.72

    DB:2.72:Reference For Writing Cobol Prog With Db2 With Atmi Calls For Oracle Tuxedo 11


    Hi..
    Am using IBM COBOL for AIX 2.0.0 on Oracle Tuxedo10g R3..
    And for database IBM DB2 Version 8.2..

    I have to write a program in Cobol with queries and with ATMI calls for Tuxedo..
    I need some reference manuals for this or some sample program..
    I also need the connectivity from cobol-DB2 to Tuxedo..

    Can anyone send me link for the same?

    The tutorial CSIMPAPP and STOCKAPP was really helpful..
    Am searching for the similar kind..

    Thanks in advance..

    Edited by: user8103349 on Mar 19, 2009 8:43 PM

    DB:2.72:Reference For Writing Cobol Prog With Db2 With Atmi Calls For Oracle Tuxedo 11

    Hi,

    Hopefully someone has some DB2 COBOL code to share. But in any case, using Tuxedo with COBOL and DB2 should be very similar to simply writing normal DB2 COBOL programs. The major difference is that Tuxedo will take care of making the connection to the database and should normally be allowed to perform all transaction management.

    From a configuration standpoint you'll need to add the appropriate line in the Tuxedo RM file that lists how Tuxedo needs to link DB2 XA libraries into the application. The connection information is provided in the OPENINFO string passed along to the TMS that you need to build for DB2 with the buildtms command, and finally you'll need to build your servers with the -r switch to tell Tuxedo which XA libraries need to be linked into the application.

    Regards,
    Todd Little
    Oracle Tuxedo Chief Architect

  • RELEVANCY SCORE 2.70

    DB:2.70:Procob In Oracle Db? jx


    DB: 9.2.0.8DB: 10.2.0.5Procob.exe and procob18.exe (I think it's to run a COBOL program) can be found at {drive}\oracle\ora92\bin on 9i server. On my 10g server, I cannot find either files in {files}\oracle\product\10.2.0\db_1\BINCan anyone please let me know where can I get the COBOL installer and explain how do I install COBOL to Oracle DB?Thanks

  • RELEVANCY SCORE 2.69

    DB:2.69:How To Call A Cobol Function From Java? 3a


    Hi all,
    I have a Cobol application running on a Linux machine. The application takes in certain inputs from the user (from the Linux command prompt) and stores them within text files in its local directory. Again when the user enters a search keyword the Cobol looksup these files and retrieves the related information on a successful search. I dont have access to the text files but I have access to the application (I have the whole Cobol application coding available with me).

    My task is to develop a Java program that would interface with this Cobol application, call the Cobol functions that do the input/output with the text files and trap the necessary output.

    Can anybody suggest how to go about this. Had the coding been in C/C++ I would have thought of usingt Java Native Interface, but how to do it for Cobol?

    Thanks in advance.

    I am posting this everywhere to get attention. Sorry for the multiple posting.
    snodx

    DB:2.69:How To Call A Cobol Function From Java? 3a

    You can use the Micr Focus Server Express. It provides the method meet you need. The tutorial is on the http://www-ufrima.imag.fr/PLACARD/ECOLE2/ASG/cobol-CD/acrobat/dp.pdf.

  • RELEVANCY SCORE 2.69

    DB:2.69:Pro*Cobol In Vms To Unix Environment kd


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

    DB:2.69:Pro*Cobol In Vms To Unix Environment kd

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

  • RELEVANCY SCORE 2.69

    DB:2.69:Environnement With Pro-Cobol And Linux Redhat 99


    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

    DB:2.69:Environnement With Pro-Cobol And Linux Redhat 99

    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

  • RELEVANCY SCORE 2.69

    DB:2.69:Sql Decode Function dc


    Oracle version: 9.2.0.1.0
    Procob version: 9.2.0.1.0
    Cobol version: 3.1.11
    O.S. version: Windows XP

    We have a pro*cobol file with the next conversion rule into a select defined with a cursor.

    NVL(TO_CHAR(A.F_ALTA,'YYYYMMDD'),' '),
    NVL(TO_CHAR(A.F_ESTADO,'YYYYMMDD'),' '),

    we store the result data through a fetch of the cursor into two variables (W-F-ALTA and W-F-ESTADO) When the program executes an insert of these two values in a target table, we define the next conversion rule:

    TO_DATE(DECODE(:W-F-ALTA,' ',NULL,:W-F-ALTA),'YYYYMMDD'),
    TO_DATE(DECODE(:W-F-ESTADO,' ',NULL,:W-F-ESTADO),'YYYYMMDD')

    Pro*Cobol and Cobol does not have errors when we precompile and compile the program but, when we execute the generated exe file, Oracle displays the next error:

    ORA-01841 (full) year must be between -4713 and +9999, and not be 0

    We think that the DECODE function is not understood by the cobol or pro*cobol interpreter. If we execute the same code without the DECODE function (only with TO_DATE function) there is no errors in the execution of the program

    somebody knows if there are reported problems with this DECODE function in Pro*Cobol or Cobol and how to solve them?

    Thanks

    DB:2.69:Sql Decode Function dc

    How have you define variable containing minus sign?

    Those are cobol language variables. Cobol allows you
    to declare variable names this way.Ah yeah, that's right, thanks Kamal to remember me that point.

    Nicolas.

  • RELEVANCY SCORE 2.69

    DB:2.69:Datatype Problems Between Java And Cobol z8


    I am calling a COBOL stored procedure from a Java Servlet. The COBOL stored procedure needs compressed numeric values and Java sends it Integer values. I'm getting an error saying my parameters don't match up. I'm wondering if it's because COBOL needs a compressed value. Has anyone else dealt with this or a similar problem? Please HELP!!!!
    Thanks so much.

    DB:2.69:Datatype Problems Between Java And Cobol z8

    I need to add more information...
    I am using JDBC. I am passing in 4 parameters from my Java code: 2 shorts and 2 ints. In the COBOL parameter definition they are 2 SMALLINTs and 2 INTEGERs. In the COBOL stored proc the 2 SMALLINTs are S9(04) comp and the 2 INTEGERs are S9(09) Usage comp. Example values that I am passing in are:

    (short) 2000
    (short) 22
    (int) 1749
    (int) 164

    The stored procedure is on a DB2 database. Hopefully this gives you a little more information to go on...
    Thanks.

  • RELEVANCY SCORE 2.68

    DB:2.68:Cobol Error.... 31


    One of my co-workers is getting a COBOL error and i was wondering if anyone here could help me decifer it.
    We use a program made by keystone and it is married to plus and minus accounting software.  I am guessing that the keystone group made this program in COBOL be cause when it gives this error it comes up in a cmd prompt window that is labeled COBOL.  The cmd prompt window scroll fills with ds error:  0018. 
    I know how to program using vb.net and some other code but I am not familiar with COBOL.  If you ask me the program married to the plus and minus stinks.  We always have problems with it.  But I feel like if I know what the error is I could possibly try to prevent it.
    So if anyone out there can help me please please let me know!
    Thanks!!

    DB:2.68:Cobol Error.... 31

    This forum is for questions about Windows Workflow Foundation not COBOL.  I would suggest contacting the manufacture of your software for assistance.

  • RELEVANCY SCORE 2.68

    DB:2.68:Pro*Cobol Not Getting Instaled On Fedora 14 x7


    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
    venki.venkat@gmail.com

    DB:2.68:Pro*Cobol Not Getting Instaled On Fedora 14 x7

    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
    venki.venkat@gmail.com

  • RELEVANCY SCORE 2.66

    DB:2.66:Re: Does Jni Work With Cobol 9p


    You can call COBOL program functions using JNI, at least if you are using MicroFocus COBOL, with NetExpress 3.0 or later. There is information about how to do this on the MicroFocus web site, www.MicroFocus.com. If you aren't using MicroFocus, then I cannot say for sure.

    DB:2.66:Re: Does Jni Work With Cobol 9p

    Have you found the solution? I have the same problem and maybe u can help me?

    Thanks a lot.

  • RELEVANCY SCORE 2.65

    DB:2.65:Pro*Cobol For Linux .. When? 19


    Does anyone have news about when we will see Pro*COBOL for the 9i database on Linux? The docs on technet simply say unavailable.

    I know it took a long time to get into the 8i product (might it have been 8.1.6 when it first appeared?).

    DB:2.65:Pro*Cobol For Linux .. When? 19

    Does anyone have news about when we will see Pro*COBOL for the 9i database on Linux? The docs on technet simply say unavailable.

    I know it took a long time to get into the 8i product (might it have been 8.1.6 when it first appeared?).

  • RELEVANCY SCORE 2.65

    DB:2.65:When Doing A Commit? ax


    Hello everyone!
    We have big cobol index files and we transfer these index files via C and OCI to a Oracle 10g database.
    The biggest files have several millions of rows to insert.
    My question is now:
    Oracle runs on our server with Suse Linux 9 on it, approximately 8 GB RAM, 2 quads.
    Does it matter, when we make a commit,
    after 500 insert statements, after 5 thousand insert statements, after 500,000 inserts?
    Thank you
    Wolfgang

    DB:2.65:When Doing A Commit? ax

    Guten Tag Nigel!
    Thank you very much for your answer.
    Wolfgang

  • RELEVANCY SCORE 2.65

    DB:2.65:Pro Cobol Directive For Setting Autocommit. xx


    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.

    DB:2.65:Pro Cobol Directive For Setting Autocommit. xx

    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.

  • RELEVANCY SCORE 2.65

    DB:2.65:Packed Decimals - Error In Data Transformation 3p


    Hi,
    I am working on converting mainframe data to xml using Format Builder version 2.01 packaged with Weblogic 8.1. These were the steps that I followed.
    Imported Copy Book in US ASCII format, Big Endian
    Saved as MFL
    Clicked Test
    Loaded the flat file containing non-xml data
    Clicked on transform non-xml to xml

    While some of the fields were translated correct, some of the packed decimal fields give the following error.
    ERROR: At MessageFormat: CPYASCII Msg:
    ERROR: At FieldFormat: o-aowing Type: Packed Msg: Malformed packed decimal number.

    Can any one let me know why this kind of error occurs while transforming data? Any help would be greatly appreciated..

    Here is the data that I transformed

    2062348494239206234849423900 00000000300000000000000032 RR0260WA00P19970725 T019941201000004254518171239315X000 00B 1FR 0 0000054768776601 WA17191 800 244-11111 800 244-1111 098040 0000 * * 20040526200406262004052600000000000000002004061319930208199503 0 0000000000000000 111111111111000000000000163FUTURE SHOP VYCOM WK#8723420 NO 2D CBR WF SHIRIN HWSF ETI400 ETC400 PE GHOLAMHOSSIEN SANII 4296 E MERCER WAY MERCER ISLAND WA 98040 0 0 20040527000000000 001XXXMHXXX1XO20040614

    Pasted below is the mfl that was created in Format Builder
    ?xml version='1.0' encoding='windows-1252'?
    !DOCTYPE MessageFormat SYSTEM 'mfl.dtd'
    !--
    ! C:\bea\user_projects\domains\MIMPOC\CPYASCII.CPY
    ! Generated: Tue Aug 23 15:02:32 IST 2005
    !
    ! revision 'WebLogic Integration 7.0.2.0' /revision
    ! date 'Tue Aug 23 15:02:32 IST 2005' /date
    ! --
    MessageFormat name='CPYASCII' version='2.01'
    StructFormat name='arfr032o'
    StructFormat name='o-zsortkey'
    !-- COBOL declaration of o-nbtn: pic x(13). 00030000(alphanum) --
    FieldFormat name='o-nbtn' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-nacct: pic x(13). 00040000(alphanum) --
    FieldFormat name='o-nacct' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-nentord: pic xx. 00050000(alphanum) --
    FieldFormat name='o-nentord' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-nentity: pic x(4). 00060000(alphanum) --
    FieldFormat name='o-nentity' type='String' length='4' codepage='US-ASCII'/
    StructFormat name='o-zdept'
    !-- COBOL declaration of o-ndeptseq: pic x. 00080000(alphanum) --
    FieldFormat name='o-ndeptseq' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ndept: pic x(6). 00090000(alphanum) --
    FieldFormat name='o-ndept' type='String' length='6' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-zsect: pic xxx. 00100000(alphanum) --
    FieldFormat name='o-zsect' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-zsortmis: pic x(13). 00110000(alphanum) --
    FieldFormat name='o-zsortmis' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-zrectype: pic xxx. 00120000(alphanum) --
    FieldFormat name='o-zrectype' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-zrecoccr: pic -9(5). 00130000(alphanum) --
    FieldFormat name='o-zrecoccr' type='Packed' length='3' decimalPlaces='2'/
    /StructFormat
    !-- COBOL declaration of o-ntypsvc: pic x. 00140000(alphanum) --
    FieldFormat name='o-ntypsvc' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nservice: pic x. 00150000(alphanum) --
    FieldFormat name='o-nservice' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nhbfreez: pic x. 00160000(alphanum) --
    FieldFormat name='o-nhbfreez' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-dblper: pic xx. 00170000(alphanum) --
    FieldFormat name='o-dblper' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-nrelease: pic x. 00180000(alphanum) --
    FieldFormat name='o-nrelease' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-njeocode: pic xx. 00190000(alphanum) --
    FieldFormat name='o-njeocode' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-itollbrk: pic x. 00200000(alphanum) --
    FieldFormat name='o-itollbrk' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ideptbil: pic x. 00210000(alphanum) --
    FieldFormat name='o-ideptbil' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nlpcexmt: pic x. 00220000(alphanum) --
    FieldFormat name='o-nlpcexmt' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-dlpcexmt: pic x(8). 00230000(alphanum) --
    FieldFormat name='o-dlpcexmt' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-alpcexmt: pic -9(7).99. 00240000(alphanum) --
    FieldFormat name='o-alpcexmt' type='Packed' length='5' decimalPlaces='2'/
    !-- COBOL declaration of o-nsotype: pic x. 00250000(alphanum) --
    FieldFormat name='o-nsotype' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nnonpub: pic x. 00260000(alphanum) --
    FieldFormat name='o-nnonpub' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-deffect: pic 9(8). 00270000(zoned,unsigned) --
    FieldFormat name='o-deffect' type='Numeric' length='8' codepage='Default'/
    !-- COBOL declaration of o-nentorg: pic x(4). 00280000(alphanum) --
    FieldFormat name='o-nentorg' type='String' length='4' codepage='US-ASCII'/
    !-- COBOL declaration of o-ndummy: pic x. 00290000(alphanum) --
    FieldFormat name='o-ndummy' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ncreftel: pic x(13). 00300000(alphanum) --
    FieldFormat name='o-ncreftel' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-nbilltyp: pic 9. 00310000(zoned,unsigned) --
    FieldFormat name='o-nbilltyp' type='Numeric' length='1' codepage='Default'/
    !-- COBOL declaration of o-nbocode: pic xxx. 00320000(alphanum) --
    FieldFormat name='o-nbocode' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-nfex: pic x. 00330000(alphanum) --
    FieldFormat name='o-nfex' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ibrc: pic x. 00340000(alphanum) --
    FieldFormat name='o-ibrc' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ngrpbill: pic x. 00350000(alphanum) --
    FieldFormat name='o-ngrpbill' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nsubtyp: pic x. 00360000(alphanum) --
    FieldFormat name='o-nsubtyp' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nfile: pic 99. 00370000(zoned,unsigned) --
    FieldFormat name='o-nfile' type='Numeric' length='2' codepage='Default'/
    StructFormat name='o-ncrclass'
    !-- COBOL declaration of o-ncrcls: pic x. 00390000(alphanum) --
    FieldFormat name='o-ncrcls' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ncrclsp: pic x. 00400000(alphanum) --
    FieldFormat name='o-ncrclsp' type='String' length='1' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-nmaincls: pic x(5). 00410000(alphanum) --
    FieldFormat name='o-nmaincls' type='String' length='5' codepage='US-ASCII'/
    !-- COBOL declaration of o-ntrunk: pic x. 00420000(alphanum) --
    FieldFormat name='o-ntrunk' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nconccls: pic x. 00430000(alphanum) --
    FieldFormat name='o-nconccls' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nsiccode: pic x(5). 00440000(alphanum) --
    FieldFormat name='o-nsiccode' type='String' length='5' codepage='US-ASCII'/
    !-- COBOL declaration of o-nsocsec: pic x(9). 00450000(alphanum) --
    FieldFormat name='o-nsocsec' type='String' length='9' codepage='US-ASCII'/
    !-- COBOL declaration of o-ntorf: pic x. 00460000(alphanum) --
    FieldFormat name='o-ntorf' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nnotrt: pic x. 00470000(alphanum) --
    FieldFormat name='o-nnotrt' type='String' length='1' codepage='US-ASCII'/
    StructFormat name='o-ztxexmt'
    !-- COBOL declaration of o-ntxexmt: occurs 12 times 00490000(array) --
    FieldFormat name='o-ntxexmt' type='String' codepage='windows-1252' repeat='12'/
    /StructFormat
    StructFormat name='o-ztar'
    !-- COBOL declaration of o-ncustst: pic xx. 00520000(alphanum) --
    FieldFormat name='o-ncustst' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-ntarsfx: pic x(4). 00530000(alphanum) --
    FieldFormat name='o-ntarsfx' type='String' length='4' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-nbillinq: pic x(14). 00540000(alphanum) --
    FieldFormat name='o-nbillinq' type='String' length='14' codepage='US-ASCII'/
    !-- COBOL declaration of o-nservinq: pic x(14). 00550000(alphanum) --
    FieldFormat name='o-nservinq' type='String' length='14' codepage='US-ASCII'/
    !-- COBOL declaration of o-ncsa: pic x(20). 00560000(alphanum) --
    FieldFormat name='o-ncsa' type='String' length='20' codepage='US-ASCII'/
    !-- COBOL declaration of o-namc: pic xx. 00570000(alphanum) --
    FieldFormat name='o-namc' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-ndiscnct: pic xx. 00580000(alphanum) --
    FieldFormat name='o-ndiscnct' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-filler1: pic xx. 00590000(alphanum) --
    FieldFormat name='o-filler1' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-nbnbacd: pic x. 00600000(alphanum) --
    FieldFormat name='o-nbnbacd' type='String' length='1' codepage='US-ASCII'/
    StructFormat name='o-zzipcode'
    !-- COBOL declaration of o-nzipcode: pic x(5). 00620000(alphanum) --
    FieldFormat name='o-nzipcode' type='String' length='5' codepage='US-ASCII'/
    !-- COBOL declaration of o-nzipsfx: pic x(4). 00630000(alphanum) --
    FieldFormat name='o-nzipsfx' type='String' length='4' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-ncarrte: pic x(4). 00640000(alphanum) --
    FieldFormat name='o-ncarrte' type='String' length='4' codepage='Default'/
    !-- COBOL declaration of o-aowing: pic -9(7).99. 00650000(alphanum) --
    FieldFormat name='o-aowing' type='Packed' length='5' decimalPlaces='2'/
    !-- COBOL declaration of o-abilled: pic -9(7).99. 00660000(alphanum) --
    FieldFormat name='o-abilled' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-abldpr: pic -9(7).99. 00670000(alphanum) --
    FieldFormat name='o-abldpr' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atotdep: pic -9(7).99. 00680000(alphanum) --
    FieldFormat name='o-atotdep' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-alocubld: pic -9(7).99. 00690000(alphanum) --
    FieldFormat name='o-alocubld' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollbld: pic -9(7).99. 00700000(alphanum) --
    FieldFormat name='o-atollbld' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollavg: pic -9(7).99. 00710000(alphanum) --
    FieldFormat name='o-atollavg' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollpr1: pic -9(7).99. 00720000(alphanum) --
    FieldFormat name='o-atollpr1' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollpr2: pic -9(7).99. 00730000(alphanum) --
    FieldFormat name='o-atollpr2' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollpr3: pic -9(7).99. 00740000(alphanum) --
    FieldFormat name='o-atollpr3' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-autm: pic -9(3). 00750000(alphanum) --
    FieldFormat name='o-autm' type='String' length='4' codepage='US-ASCII'/
    !-- COBOL declaration of o-abocamt: pic -9(3).99. 00760000(alphanum) --
    FieldFormat name='o-abocamt' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-apnbfwo: pic -9(3).99. 00770000(alphanum) --
    FieldFormat name='o-apnbfwo' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-aattcbld: pic -9(3).99. 00780000(alphanum) --
    FieldFormat name='o-aattcbld' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-afconcaj: pic -9(3).99. 00790000(alphanum) --
    FieldFormat name='o-afconcaj' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-aftotdue: pic -9(3).99. 00800000(alphanum) --
    FieldFormat name='o-aftotdue' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-abaldue: pic -9(7).99. 00810000(alphanum) --
    FieldFormat name='o-abaldue' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atotcchg: pic -9(7).99. 00820000(alphanum) --
    FieldFormat name='o-atotcchg' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-dfromdt: pic x(8). 00830000(alphanum) --
    FieldFormat name='o-dfromdt' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dtodt: pic x(8). 00840000(alphanum) --
    FieldFormat name='o-dtodt' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dbill: pic x(8). 00850000(alphanum) --
    FieldFormat name='o-dbill' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dfbill: pic x(8). 00860000(alphanum) --
    FieldFormat name='o-dfbill' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-drvsdfb: pic x(8). 00870000(alphanum) --
    FieldFormat name='o-drvsdfb' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dpaydue: pic x(8). 00880000(alphanum) --
    FieldFormat name='o-dpaydue' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-destacct: pic 9(8). 00890000(zoned,unsigned) --
    FieldFormat name='o-destacct' type='UZonedDecimal' length='8'/
    !-- COBOL declaration of o-dcrchkd: pic 9(6). 00900000(zoned,unsigned) --
    FieldFormat name='o-dcrchkd' type='UZonedDecimal' length='6'/
    !-- COBOL declaration of o-dcrclass: pic x(4). 00910000(alphanum) --
    FieldFormat name='o-dcrclass' type='String' length='4' codepage='US-ASCII'/
    !-- COBOL declaration of o-nnobill: pic x. 00920000(alphanum) --
    FieldFormat name='o-nnobill' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nrsid: pic xxx. 00930000(alphanum) --
    FieldFormat name='o-nrsid' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-nzcid: pic xxx. 00940000(alphanum) --
    FieldFormat name='o-nzcid' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-ntypelms: pic x. 00950000(alphanum) --
    FieldFormat name='o-ntypelms' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-dgar: pic 9(8). 01000000(zoned,unsigned) --
    FieldFormat name='o-dgar' type='UZonedDecimal' length='8'/
    !-- COBOL declaration of o-dwrtnoff: pic 9(8). 01010000(zoned,unsigned) --
    FieldFormat name='o-dwrtnoff' type='UZonedDecimal' length='8'/
    !-- COBOL declaration of o-zacctgar: pic x(13). 01020000(alphanum) --
    FieldFormat name='o-zacctgar' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-ztrthist: pic x(12). 01030000(alphanum) --
    FieldFormat name='o-ztrthist' type='String' length='12' codepage='US-ASCII'/
    !-- COBOL declaration of o-znsfhist: pic x(12). 01040000(alphanum) --
    FieldFormat name='o-znsfhist' type='String' length='12' codepage='US-ASCII'/
    !-- COBOL declaration of o-nrao: pic xxx. 01050000(alphanum) --
    FieldFormat name='o-nrao' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-zcrall: pic x(150). 01060000(alphanum) --
    FieldFormat name='o-zcrall' type='String' length='150' codepage='US-ASCII'/
    !-- COBOL declaration of o-zmail1: pic x(30). 01070000(alphanum) --
    FieldFormat name='o-zmail1' type='String' length='30' codepage='US-ASCII'/
    !-- COBOL declaration of o-zmail2: pic x(30). 01080000(alphanum) --
    FieldFormat name='o-zmail2' type='String' length='30' codepage='US-ASCII'/
    !-- COBOL declaration of o-zmail3: pic x(30). 01090000(alphanum) --
    FieldFormat name='o-zmail3' type='String' length='30' codepage='US-ASCII'/
    !-- COBOL declaration of o-zmail4: pic x(30). 01100000(alphanum) --
    FieldFormat name='o-zmail4' type='String' length='30' codepage='US-ASCII'/
    StructFormat name='o-zselbill'
    !-- COBOL declaration of o-iselbill: occurs 12 times 01120000(array) --
    FieldFormat name='o-iselbill' type='String' delim='\\x00' repeat='12'/
    /StructFormat
    !-- COBOL declaration of o-irsb: pic x. 01140000(alphanum) --
    FieldFormat name='o-irsb' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-imcipic: pic x. 01170000(alphanum) --
    FieldFormat name='o-imcipic' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcicid: pic x(8). 01180000(alphanum) --
    FieldFormat name='o-nmcicid' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-nspldist: pic x. 01190000(alphanum) --
    FieldFormat name='o-nspldist' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-artdeal: pic -9(7).99. 01200000(alphanum) --
    FieldFormat name='o-artdeal' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-dbextdat: pic x(8). 01210000(alphanum) --
    FieldFormat name='o-dbextdat' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dreferal: pic 9(8). 01220000(zoned,unsigned) --
    FieldFormat name='o-dreferal' type='UZonedDecimal' length='8'/
    !-- COBOL declaration of o-iattbal: pic x. 01230000(alphanum) --
    FieldFormat name='o-iattbal' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nrtdeal: pic x. 01240000(alphanum) --
    FieldFormat name='o-nrtdeal' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-noccurs: pic -9(5). 01250000(alphanum) --
    FieldFormat name='o-noccurs' type='String' length='6' codepage='US-ASCII'/
    !-- COBOL declaration of o-nhbreas: occurs 40 times 01260000(array) --
    FieldFormat name='o-nhbreas' type='String' delim='\\x00' repeat='40'/
    !-- COBOL declaration of o-alocupr1: pic -9(7).99. 01280000(alphanum) --
    FieldFormat name='o-alocupr1' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-alocupr2: pic -9(7).99. 01290000(alphanum) --
    FieldFormat name='o-alocupr2' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-alocupr3: pic -9(7).99. 01300000(alphanum) --
    FieldFormat name='o-alocupr3' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-alocuavg: pic -9(7).99. 01310000(alphanum) --
    FieldFormat name='o-alocuavg' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-nsplitbl: pic x. 01320000(alphanum) --
    FieldFormat name='o-nsplitbl' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-npkg: pic x. 01330000(alphanum) --
    FieldFormat name='o-npkg' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcntype: pic x. 01340000(alphanum) --
    FieldFormat name='o-nmcntype' type='String' length='1' codepage='US-ASCII'/
    StructFormat name='o-zmcnnum1'
    StructFormat name='o-zfccrpt1'
    !-- COBOL declaration of o-nmcncpe1: pic x. 01370000(alphanum) --
    FieldFormat name='o-nmcncpe1' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcnona1: pic x. 01380000(alphanum) --
    FieldFormat name='o-nmcnona1' type='String' length='1' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-nmcnintc: pic x. 01390000(alphanum) --
    FieldFormat name='o-nmcnintc' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcnstat: pic x. 01400000(alphanum) --
    FieldFormat name='o-nmcnstat' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmktunit: pic x. 01410000(alphanum) --
    FieldFormat name='o-nmktunit' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcnrest: pic x(6). 01420000(alphanum) --
    FieldFormat name='o-nmcnrest' type='String' length='6' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-dautopa: pic x(8). 01430000(alphanum) --
    FieldFormat name='o-dautopa' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-nexk: pic x(6). 01440000(alphanum) --
    FieldFormat name='o-nexk' type='String' length='6' codepage='US-ASCII'/
    !-- COBOL declaration of o-mktmsg-usoc-ind: pic x(5). 01450000(alphanum) --
    FieldFormat name='o-mktmsg-usoc-ind' type='String' length='5' codepage='US-ASCII'/
    !-- COBOL declaration of o-filler2: pic x(5). 01460000(alphanum) --
    FieldFormat name='o-filler2' type='String' length='5' codepage='US-ASCII'/
    /StructFormat
    /MessageFormat

    DB:2.65:Packed Decimals - Error In Data Transformation 3p

    Hi,
    I am working on converting mainframe data to xml using Format Builder version 2.01 packaged with Weblogic 8.1. These were the steps that I followed.
    Imported Copy Book in US ASCII format, Big Endian
    Saved as MFL
    Clicked Test
    Loaded the flat file containing non-xml data
    Clicked on transform non-xml to xml

    While some of the fields were translated correct, some of the packed decimal fields give the following error.
    ERROR: At MessageFormat: CPYASCII Msg:
    ERROR: At FieldFormat: o-aowing Type: Packed Msg: Malformed packed decimal number.

    Can any one let me know why this kind of error occurs while transforming data? Any help would be greatly appreciated..

    Here is the data that I transformed

    2062348494239206234849423900 00000000300000000000000032 RR0260WA00P19970725 T019941201000004254518171239315X000 00B 1FR 0 0000054768776601 WA17191 800 244-11111 800 244-1111 098040 0000 * * 20040526200406262004052600000000000000002004061319930208199503 0 0000000000000000 111111111111000000000000163FUTURE SHOP VYCOM WK#8723420 NO 2D CBR WF SHIRIN HWSF ETI400 ETC400 PE GHOLAMHOSSIEN SANII 4296 E MERCER WAY MERCER ISLAND WA 98040 0 0 20040527000000000 001XXXMHXXX1XO20040614

    Pasted below is the mfl that was created in Format Builder
    ?xml version='1.0' encoding='windows-1252'?
    !DOCTYPE MessageFormat SYSTEM 'mfl.dtd'
    !--
    ! C:\bea\user_projects\domains\MIMPOC\CPYASCII.CPY
    ! Generated: Tue Aug 23 15:02:32 IST 2005
    !
    ! revision 'WebLogic Integration 7.0.2.0' /revision
    ! date 'Tue Aug 23 15:02:32 IST 2005' /date
    ! --
    MessageFormat name='CPYASCII' version='2.01'
    StructFormat name='arfr032o'
    StructFormat name='o-zsortkey'
    !-- COBOL declaration of o-nbtn: pic x(13). 00030000(alphanum) --
    FieldFormat name='o-nbtn' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-nacct: pic x(13). 00040000(alphanum) --
    FieldFormat name='o-nacct' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-nentord: pic xx. 00050000(alphanum) --
    FieldFormat name='o-nentord' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-nentity: pic x(4). 00060000(alphanum) --
    FieldFormat name='o-nentity' type='String' length='4' codepage='US-ASCII'/
    StructFormat name='o-zdept'
    !-- COBOL declaration of o-ndeptseq: pic x. 00080000(alphanum) --
    FieldFormat name='o-ndeptseq' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ndept: pic x(6). 00090000(alphanum) --
    FieldFormat name='o-ndept' type='String' length='6' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-zsect: pic xxx. 00100000(alphanum) --
    FieldFormat name='o-zsect' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-zsortmis: pic x(13). 00110000(alphanum) --
    FieldFormat name='o-zsortmis' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-zrectype: pic xxx. 00120000(alphanum) --
    FieldFormat name='o-zrectype' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-zrecoccr: pic -9(5). 00130000(alphanum) --
    FieldFormat name='o-zrecoccr' type='Packed' length='3' decimalPlaces='2'/
    /StructFormat
    !-- COBOL declaration of o-ntypsvc: pic x. 00140000(alphanum) --
    FieldFormat name='o-ntypsvc' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nservice: pic x. 00150000(alphanum) --
    FieldFormat name='o-nservice' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nhbfreez: pic x. 00160000(alphanum) --
    FieldFormat name='o-nhbfreez' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-dblper: pic xx. 00170000(alphanum) --
    FieldFormat name='o-dblper' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-nrelease: pic x. 00180000(alphanum) --
    FieldFormat name='o-nrelease' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-njeocode: pic xx. 00190000(alphanum) --
    FieldFormat name='o-njeocode' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-itollbrk: pic x. 00200000(alphanum) --
    FieldFormat name='o-itollbrk' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ideptbil: pic x. 00210000(alphanum) --
    FieldFormat name='o-ideptbil' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nlpcexmt: pic x. 00220000(alphanum) --
    FieldFormat name='o-nlpcexmt' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-dlpcexmt: pic x(8). 00230000(alphanum) --
    FieldFormat name='o-dlpcexmt' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-alpcexmt: pic -9(7).99. 00240000(alphanum) --
    FieldFormat name='o-alpcexmt' type='Packed' length='5' decimalPlaces='2'/
    !-- COBOL declaration of o-nsotype: pic x. 00250000(alphanum) --
    FieldFormat name='o-nsotype' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nnonpub: pic x. 00260000(alphanum) --
    FieldFormat name='o-nnonpub' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-deffect: pic 9(8). 00270000(zoned,unsigned) --
    FieldFormat name='o-deffect' type='Numeric' length='8' codepage='Default'/
    !-- COBOL declaration of o-nentorg: pic x(4). 00280000(alphanum) --
    FieldFormat name='o-nentorg' type='String' length='4' codepage='US-ASCII'/
    !-- COBOL declaration of o-ndummy: pic x. 00290000(alphanum) --
    FieldFormat name='o-ndummy' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ncreftel: pic x(13). 00300000(alphanum) --
    FieldFormat name='o-ncreftel' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-nbilltyp: pic 9. 00310000(zoned,unsigned) --
    FieldFormat name='o-nbilltyp' type='Numeric' length='1' codepage='Default'/
    !-- COBOL declaration of o-nbocode: pic xxx. 00320000(alphanum) --
    FieldFormat name='o-nbocode' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-nfex: pic x. 00330000(alphanum) --
    FieldFormat name='o-nfex' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ibrc: pic x. 00340000(alphanum) --
    FieldFormat name='o-ibrc' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ngrpbill: pic x. 00350000(alphanum) --
    FieldFormat name='o-ngrpbill' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nsubtyp: pic x. 00360000(alphanum) --
    FieldFormat name='o-nsubtyp' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nfile: pic 99. 00370000(zoned,unsigned) --
    FieldFormat name='o-nfile' type='Numeric' length='2' codepage='Default'/
    StructFormat name='o-ncrclass'
    !-- COBOL declaration of o-ncrcls: pic x. 00390000(alphanum) --
    FieldFormat name='o-ncrcls' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-ncrclsp: pic x. 00400000(alphanum) --
    FieldFormat name='o-ncrclsp' type='String' length='1' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-nmaincls: pic x(5). 00410000(alphanum) --
    FieldFormat name='o-nmaincls' type='String' length='5' codepage='US-ASCII'/
    !-- COBOL declaration of o-ntrunk: pic x. 00420000(alphanum) --
    FieldFormat name='o-ntrunk' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nconccls: pic x. 00430000(alphanum) --
    FieldFormat name='o-nconccls' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nsiccode: pic x(5). 00440000(alphanum) --
    FieldFormat name='o-nsiccode' type='String' length='5' codepage='US-ASCII'/
    !-- COBOL declaration of o-nsocsec: pic x(9). 00450000(alphanum) --
    FieldFormat name='o-nsocsec' type='String' length='9' codepage='US-ASCII'/
    !-- COBOL declaration of o-ntorf: pic x. 00460000(alphanum) --
    FieldFormat name='o-ntorf' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nnotrt: pic x. 00470000(alphanum) --
    FieldFormat name='o-nnotrt' type='String' length='1' codepage='US-ASCII'/
    StructFormat name='o-ztxexmt'
    !-- COBOL declaration of o-ntxexmt: occurs 12 times 00490000(array) --
    FieldFormat name='o-ntxexmt' type='String' codepage='windows-1252' repeat='12'/
    /StructFormat
    StructFormat name='o-ztar'
    !-- COBOL declaration of o-ncustst: pic xx. 00520000(alphanum) --
    FieldFormat name='o-ncustst' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-ntarsfx: pic x(4). 00530000(alphanum) --
    FieldFormat name='o-ntarsfx' type='String' length='4' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-nbillinq: pic x(14). 00540000(alphanum) --
    FieldFormat name='o-nbillinq' type='String' length='14' codepage='US-ASCII'/
    !-- COBOL declaration of o-nservinq: pic x(14). 00550000(alphanum) --
    FieldFormat name='o-nservinq' type='String' length='14' codepage='US-ASCII'/
    !-- COBOL declaration of o-ncsa: pic x(20). 00560000(alphanum) --
    FieldFormat name='o-ncsa' type='String' length='20' codepage='US-ASCII'/
    !-- COBOL declaration of o-namc: pic xx. 00570000(alphanum) --
    FieldFormat name='o-namc' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-ndiscnct: pic xx. 00580000(alphanum) --
    FieldFormat name='o-ndiscnct' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-filler1: pic xx. 00590000(alphanum) --
    FieldFormat name='o-filler1' type='String' length='2' codepage='US-ASCII'/
    !-- COBOL declaration of o-nbnbacd: pic x. 00600000(alphanum) --
    FieldFormat name='o-nbnbacd' type='String' length='1' codepage='US-ASCII'/
    StructFormat name='o-zzipcode'
    !-- COBOL declaration of o-nzipcode: pic x(5). 00620000(alphanum) --
    FieldFormat name='o-nzipcode' type='String' length='5' codepage='US-ASCII'/
    !-- COBOL declaration of o-nzipsfx: pic x(4). 00630000(alphanum) --
    FieldFormat name='o-nzipsfx' type='String' length='4' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-ncarrte: pic x(4). 00640000(alphanum) --
    FieldFormat name='o-ncarrte' type='String' length='4' codepage='Default'/
    !-- COBOL declaration of o-aowing: pic -9(7).99. 00650000(alphanum) --
    FieldFormat name='o-aowing' type='Packed' length='5' decimalPlaces='2'/
    !-- COBOL declaration of o-abilled: pic -9(7).99. 00660000(alphanum) --
    FieldFormat name='o-abilled' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-abldpr: pic -9(7).99. 00670000(alphanum) --
    FieldFormat name='o-abldpr' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atotdep: pic -9(7).99. 00680000(alphanum) --
    FieldFormat name='o-atotdep' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-alocubld: pic -9(7).99. 00690000(alphanum) --
    FieldFormat name='o-alocubld' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollbld: pic -9(7).99. 00700000(alphanum) --
    FieldFormat name='o-atollbld' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollavg: pic -9(7).99. 00710000(alphanum) --
    FieldFormat name='o-atollavg' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollpr1: pic -9(7).99. 00720000(alphanum) --
    FieldFormat name='o-atollpr1' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollpr2: pic -9(7).99. 00730000(alphanum) --
    FieldFormat name='o-atollpr2' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atollpr3: pic -9(7).99. 00740000(alphanum) --
    FieldFormat name='o-atollpr3' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-autm: pic -9(3). 00750000(alphanum) --
    FieldFormat name='o-autm' type='String' length='4' codepage='US-ASCII'/
    !-- COBOL declaration of o-abocamt: pic -9(3).99. 00760000(alphanum) --
    FieldFormat name='o-abocamt' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-apnbfwo: pic -9(3).99. 00770000(alphanum) --
    FieldFormat name='o-apnbfwo' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-aattcbld: pic -9(3).99. 00780000(alphanum) --
    FieldFormat name='o-aattcbld' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-afconcaj: pic -9(3).99. 00790000(alphanum) --
    FieldFormat name='o-afconcaj' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-aftotdue: pic -9(3).99. 00800000(alphanum) --
    FieldFormat name='o-aftotdue' type='String' length='7' codepage='US-ASCII'/
    !-- COBOL declaration of o-abaldue: pic -9(7).99. 00810000(alphanum) --
    FieldFormat name='o-abaldue' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-atotcchg: pic -9(7).99. 00820000(alphanum) --
    FieldFormat name='o-atotcchg' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-dfromdt: pic x(8). 00830000(alphanum) --
    FieldFormat name='o-dfromdt' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dtodt: pic x(8). 00840000(alphanum) --
    FieldFormat name='o-dtodt' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dbill: pic x(8). 00850000(alphanum) --
    FieldFormat name='o-dbill' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dfbill: pic x(8). 00860000(alphanum) --
    FieldFormat name='o-dfbill' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-drvsdfb: pic x(8). 00870000(alphanum) --
    FieldFormat name='o-drvsdfb' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dpaydue: pic x(8). 00880000(alphanum) --
    FieldFormat name='o-dpaydue' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-destacct: pic 9(8). 00890000(zoned,unsigned) --
    FieldFormat name='o-destacct' type='UZonedDecimal' length='8'/
    !-- COBOL declaration of o-dcrchkd: pic 9(6). 00900000(zoned,unsigned) --
    FieldFormat name='o-dcrchkd' type='UZonedDecimal' length='6'/
    !-- COBOL declaration of o-dcrclass: pic x(4). 00910000(alphanum) --
    FieldFormat name='o-dcrclass' type='String' length='4' codepage='US-ASCII'/
    !-- COBOL declaration of o-nnobill: pic x. 00920000(alphanum) --
    FieldFormat name='o-nnobill' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nrsid: pic xxx. 00930000(alphanum) --
    FieldFormat name='o-nrsid' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-nzcid: pic xxx. 00940000(alphanum) --
    FieldFormat name='o-nzcid' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-ntypelms: pic x. 00950000(alphanum) --
    FieldFormat name='o-ntypelms' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-dgar: pic 9(8). 01000000(zoned,unsigned) --
    FieldFormat name='o-dgar' type='UZonedDecimal' length='8'/
    !-- COBOL declaration of o-dwrtnoff: pic 9(8). 01010000(zoned,unsigned) --
    FieldFormat name='o-dwrtnoff' type='UZonedDecimal' length='8'/
    !-- COBOL declaration of o-zacctgar: pic x(13). 01020000(alphanum) --
    FieldFormat name='o-zacctgar' type='String' length='13' codepage='US-ASCII'/
    !-- COBOL declaration of o-ztrthist: pic x(12). 01030000(alphanum) --
    FieldFormat name='o-ztrthist' type='String' length='12' codepage='US-ASCII'/
    !-- COBOL declaration of o-znsfhist: pic x(12). 01040000(alphanum) --
    FieldFormat name='o-znsfhist' type='String' length='12' codepage='US-ASCII'/
    !-- COBOL declaration of o-nrao: pic xxx. 01050000(alphanum) --
    FieldFormat name='o-nrao' type='String' length='3' codepage='US-ASCII'/
    !-- COBOL declaration of o-zcrall: pic x(150). 01060000(alphanum) --
    FieldFormat name='o-zcrall' type='String' length='150' codepage='US-ASCII'/
    !-- COBOL declaration of o-zmail1: pic x(30). 01070000(alphanum) --
    FieldFormat name='o-zmail1' type='String' length='30' codepage='US-ASCII'/
    !-- COBOL declaration of o-zmail2: pic x(30). 01080000(alphanum) --
    FieldFormat name='o-zmail2' type='String' length='30' codepage='US-ASCII'/
    !-- COBOL declaration of o-zmail3: pic x(30). 01090000(alphanum) --
    FieldFormat name='o-zmail3' type='String' length='30' codepage='US-ASCII'/
    !-- COBOL declaration of o-zmail4: pic x(30). 01100000(alphanum) --
    FieldFormat name='o-zmail4' type='String' length='30' codepage='US-ASCII'/
    StructFormat name='o-zselbill'
    !-- COBOL declaration of o-iselbill: occurs 12 times 01120000(array) --
    FieldFormat name='o-iselbill' type='String' delim='\\x00' repeat='12'/
    /StructFormat
    !-- COBOL declaration of o-irsb: pic x. 01140000(alphanum) --
    FieldFormat name='o-irsb' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-imcipic: pic x. 01170000(alphanum) --
    FieldFormat name='o-imcipic' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcicid: pic x(8). 01180000(alphanum) --
    FieldFormat name='o-nmcicid' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-nspldist: pic x. 01190000(alphanum) --
    FieldFormat name='o-nspldist' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-artdeal: pic -9(7).99. 01200000(alphanum) --
    FieldFormat name='o-artdeal' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-dbextdat: pic x(8). 01210000(alphanum) --
    FieldFormat name='o-dbextdat' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-dreferal: pic 9(8). 01220000(zoned,unsigned) --
    FieldFormat name='o-dreferal' type='UZonedDecimal' length='8'/
    !-- COBOL declaration of o-iattbal: pic x. 01230000(alphanum) --
    FieldFormat name='o-iattbal' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nrtdeal: pic x. 01240000(alphanum) --
    FieldFormat name='o-nrtdeal' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-noccurs: pic -9(5). 01250000(alphanum) --
    FieldFormat name='o-noccurs' type='String' length='6' codepage='US-ASCII'/
    !-- COBOL declaration of o-nhbreas: occurs 40 times 01260000(array) --
    FieldFormat name='o-nhbreas' type='String' delim='\\x00' repeat='40'/
    !-- COBOL declaration of o-alocupr1: pic -9(7).99. 01280000(alphanum) --
    FieldFormat name='o-alocupr1' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-alocupr2: pic -9(7).99. 01290000(alphanum) --
    FieldFormat name='o-alocupr2' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-alocupr3: pic -9(7).99. 01300000(alphanum) --
    FieldFormat name='o-alocupr3' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-alocuavg: pic -9(7).99. 01310000(alphanum) --
    FieldFormat name='o-alocuavg' type='String' length='11' codepage='US-ASCII'/
    !-- COBOL declaration of o-nsplitbl: pic x. 01320000(alphanum) --
    FieldFormat name='o-nsplitbl' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-npkg: pic x. 01330000(alphanum) --
    FieldFormat name='o-npkg' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcntype: pic x. 01340000(alphanum) --
    FieldFormat name='o-nmcntype' type='String' length='1' codepage='US-ASCII'/
    StructFormat name='o-zmcnnum1'
    StructFormat name='o-zfccrpt1'
    !-- COBOL declaration of o-nmcncpe1: pic x. 01370000(alphanum) --
    FieldFormat name='o-nmcncpe1' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcnona1: pic x. 01380000(alphanum) --
    FieldFormat name='o-nmcnona1' type='String' length='1' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-nmcnintc: pic x. 01390000(alphanum) --
    FieldFormat name='o-nmcnintc' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcnstat: pic x. 01400000(alphanum) --
    FieldFormat name='o-nmcnstat' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmktunit: pic x. 01410000(alphanum) --
    FieldFormat name='o-nmktunit' type='String' length='1' codepage='US-ASCII'/
    !-- COBOL declaration of o-nmcnrest: pic x(6). 01420000(alphanum) --
    FieldFormat name='o-nmcnrest' type='String' length='6' codepage='US-ASCII'/
    /StructFormat
    !-- COBOL declaration of o-dautopa: pic x(8). 01430000(alphanum) --
    FieldFormat name='o-dautopa' type='String' length='8' codepage='US-ASCII'/
    !-- COBOL declaration of o-nexk: pic x(6). 01440000(alphanum) --
    FieldFormat name='o-nexk' type='String' length='6' codepage='US-ASCII'/
    !-- COBOL declaration of o-mktmsg-usoc-ind: pic x(5). 01450000(alphanum) --
    FieldFormat name='o-mktmsg-usoc-ind' type='String' length='5' codepage='US-ASCII'/
    !-- COBOL declaration of o-filler2: pic x(5). 01460000(alphanum) --
    FieldFormat name='o-filler2' type='String' length='5' codepage='US-ASCII'/
    /StructFormat
    /MessageFormat

  • RELEVANCY SCORE 2.65

    DB:2.65:Precompilers On Xe pc


    Hi all,
    Does anyone knows if oracle XE includes pre-compilers? I wanted to use cobol to write a program that accesses a XE database. I know that for the 10g enterprise edition, pro-cobol comes in the client CD. I believe i can't use this client with XE...

    Thank you

    DB:2.65:Precompilers On Xe pc

    Hi all,
    Does anyone knows if oracle XE includes pre-compilers? I wanted to use cobol to write a program that accesses a XE database. I know that for the 10g enterprise edition, pro-cobol comes in the client CD. I believe i can't use this client with XE...

    Thank you

  • RELEVANCY SCORE 2.65

    DB:2.65:Can't Compile Old Cobol Programs With Oracle9i Pro*Cobol. ss


    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

    DB:2.65:Can't Compile Old Cobol Programs With Oracle9i Pro*Cobol. ss

    ...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

  • RELEVANCY SCORE 2.64

    DB:2.64:Does Ibm Cobol Supports Oracle Db? 77


    Hi..

    Am using IBM COBOL for AIX version 2.0.0 with Oracle Tuxedo10g..

    I need to know whether there is connectivity between IBM COBOL and Oracle DB or is there any limitations..
    I need to embed the SQL query with IBM COBOL..

    Thanks..

    DB:2.64:Does Ibm Cobol Supports Oracle Db? 77

    I will agree with Naveed, Oracle supports Pro*COBOL and if the Oracle database is remote you would need an Oracle client on the server where the COBOL program is going to run. If the Oracle database is local then hopefully the necessary libraries were already installed with Oracle.

    IBM is big on supporting java and java would be an alternative choice for accessing Oracle if Pro*COBOL is not available and cannot be installed.

    HTH -- Mark D Powell --

  • RELEVANCY SCORE 2.63

    DB:2.63:Compilation Error k9


    Hi all,

    We have two Identical servers DEV1 and PROD1 with same SunOS and Oracle Db versions.

    Then we have a pro*cobol program "prog1" which compile clean at DEV1, but when copied to PROD1 and compiled it does not
    go clean compile.

    Can you help me how to troubleshoot this problem please.

    Is there a bug in Oracle pro*cobol that I may not be aware of?

    How do I compare the pro*cobol version of the 2 servers?

    I also tried to check the server OS versions:

    @DEV1

    uname -a

    SunOS DEV1 5.10 Generic_144488-12 sun4v sparc SUNW,T5440

    @PROD1

    uname -a

    SunOS PROD1 5.10 Generic_118833-17 sun4u sparc SUNW,Sun-Fire-V440Are our OS in sync?

    MF cobol version:

    check cobrun:

    DEV1 MF Cobol Version:
    V5.1 revision 0 build 10/10/2 G; 07109. Run Time System RXCTI/AA0/00000Q.

    DEV2 MF Cobol Version:
    V5.1 revision 0 build 10/10/2 G; 07209. Run Time System RXCTI/AA0/00000QIs our cobol compiler in sync?

    Thanks a lot,

    DB:2.63:Compilation Error k9

    This forum is for general database questions. Unfortunately there's no dedicated Cobol forum, but since it could be a generic pre-compiler/compiler configuration problem, you may address the question to this forum:

    https://forums.oracle.com/forums/category.jspa?categoryID=280

  • RELEVANCY SCORE 2.63

    DB:2.63:Pro*Cobol, Linux &Amp; Oracle 9i xk


    There is an old Oracle 7.3.4-based application on a very old Unix. The application is written in Cobol and evidently used Oracle's Pro*Cobol precompiler product.

    Now, we're porting to Oracle 9i, possibly powered by Linux. I can't find Pro*Cobol for anything past Oracle 8. Was Pro*Cobol functionally replaced by something else? Is that (or its equivalent) still needed? Thanks in advance.

    (My email is patk@conservor.com)

    DB:2.63:Pro*Cobol, Linux &Amp; Oracle 9i xk

    Here was my answer to the same questions posted in the precompiler forum yesterday...news is not good....

    From: ted.broadfield@nisc.cc 04-Nov-02 20:13
    Subject: Pro*Cobol precompiler under Intel Linux Availability??

    Pro*Cobol precompiler under Intel Linux Availability??

    I am looking for the Pro*Cobol precompiler for Oracle 9i Database Enterprise Edition (any version) running on Intel Linux (Advanced Server or Redhat).

    My developer can not seem to find this precompiler that is supported in Intel Linux for 9i. (We see it is available under True54 Unix and other 64-bit OS's but not for Linux)

    Does Oracle offer this? Where can we find it? If not, can an older Pro*Cobal precomiler from, say, Oracle 8i port over and work under 9i? If not, is Oracle planning on releasing the Pro*Cobol precompiler under 9i? If so when?

    To date we have had very little success getting an answer on this specific area of questioning. Any response, even that it will not be available, will help us determine a best plan of attack on our development.

    Ted

    --------------------------------------------------------------------------------

    From: Oracle, Giridhar Tatavarty 05-Nov-02 09:01
    Subject: Re : Pro*Cobol precompiler under Intel Linux Availability??

    Hi ,
    Pro*Cobol is not shipped / supported with Oracle 9i Database on Linux. I am not aware of any plans to support it in future too .Using 8i port is not recommended because Pro*cobol is not supported on Linux platform.
    Regards,
    Giridhar

  • RELEVANCY SCORE 2.63

    DB:2.63:Cobol Sources With Redefines/Occurs/Comp Formats kc



    Hi, Can anyone share a step by step approach on how to create informatica mapping for Mainframe Cobol sources ? Cobol source has the following layout options.

    1. Layout has Occurs

    2.Layout has comp/comp-3 numeric formats

    3.Layout has REDEFINES clauses.

    I was trying to develop a mapping but struck at redefines/comp/comp-3 formats.

    Appreciate your quick response.

    Thanks

    Kr.

    DB:2.63:Cobol Sources With Redefines/Occurs/Comp Formats kc


    Hi Kishore

    I have not worked on COBOL files. I have found the following example from Informatica Marketplace website. Hope it will give you clue for your task.

    https://community.informatica.com/solutions/mapping_vsam_cobol_file

    Regards

    Kiran Ghatage

  • RELEVANCY SCORE 2.63

    DB:2.63:Oracle 10g Client On Win Xp Pro Opens An Extra Dos Window? 9c


    Just got thru upgrading from 9.2 to 10g r2 and SAs installed the 10g client. They say they installed Oracle Enterprise Manager (OEM) for 10g. It has correct tnsnames and starts up. It first opens a DOS window than an OEM window. Both windows stay, if you close one the other also closes. What's with this extra DOS window and how do i get rid of it? I have other power-users that do not have privs to have dos windows so this causes big problems - I've read somewhere that it has something to do with Java.

    DB:2.63:Oracle 10g Client On Win Xp Pro Opens An Extra Dos Window? 9c

    Hi,

    i take it that this is a known occurance with the 10g enterprise manager?
    It is exactly what Fredrik said. OEM executes oemapp batch file.

    Cheers

  • RELEVANCY SCORE 2.63

    DB:2.63:Sample Microfocus Cobol Static Sql Apps kd


    Does anyone know where I might be able to get a sample MicroFocus COBOL application for use with Oracle 8.0.6 and 8.1.6? I am not a COBOL programmer and need the information for a COBOL programmer who knows nothing about SQL.

    DB:2.63:Sample Microfocus Cobol Static Sql Apps kd

    Does anyone know where I might be able to get a sample MicroFocus COBOL application for use with Oracle 8.0.6 and 8.1.6? I am not a COBOL programmer and need the information for a COBOL programmer who knows nothing about SQL.

  • RELEVANCY SCORE 2.62

    DB:2.62:11g Install Fails On Check Network Reqs - 10g Installs Fine (Xp Pro Sp3) mp


    I am trying to install Oracle 11g on an XP Pro SP 3 machine.
    It fails every time on the "checking network requirements." Javaw,exe crashes
    I have a loop back adapter.
    I've tried disabling all other network connections, turning off the firewall - no good.

    The odd thing is 10g installs with No Problems on he same system.

    Any ideas?

    DB:2.62:11g Install Fails On Check Network Reqs - 10g Installs Fine (Xp Pro Sp3) mp

    I tried that - disabled AV and turned off windows firewall- same crash/result.
    This is so weird.10g has no problem installing in the same setting.
    This whole business has forced me to learn how to install 11g into Ubuntu on a VM image - so I have access to 11g and am ok - but still - this is weird - and shouldn't be so hard!
    thanks

  • RELEVANCY SCORE 2.62

    DB:2.62:Api To Allow Cobol To Interface With Jms xx


    Is there any interface to connect with JMS from COBOL??

    DB:2.62:Api To Allow Cobol To Interface With Jms xx

    Or find what messaging system JMS is talking to and find the Cobol API for that.

  • RELEVANCY SCORE 2.62

    DB:2.62:A Cobol Application And Linux Driver 9z


    Hi,

    I'm trying to make work a tiny-cobol application that has embeded sql senteces and queries data from an Oracle Database 9.2, on the same machine with a Linux Advanced Server 8.2 platform.

    If these two were intalled on a Windows platform, an ODBC driver would be the middle device that would make them have communication. so, what is the appropiate tool on linux that would make a cobol application retrieve data from an Oracle database?

    DB:2.62:A Cobol Application And Linux Driver 9z

    You can either use PRO*COBOL or ORACLE OCI, this if you have one of the following compilers.

    MicroFocus
    RM/COBOL V8

  • RELEVANCY SCORE 2.62

    DB:2.62:Perl And Pro*C From Oracle 9i To Oracle 10g k8


    Hi to all,
    on HP-UX 11 I have migrated form Oracle 9i to 10g R2 and I have some problems with Perl and pro*C scripts during connection to rdbms database.
    Shell I reinstall or migerate Perl and pro*C ?

    Is anybody there who can help me?

    DB:2.62:Perl And Pro*C From Oracle 9i To Oracle 10g k8

    Hi,
    No problem, it's easy to get confused about the different forums. Someone here amy be able to help but a language forum is the best option.

    Regards,
    Mike

  • RELEVANCY SCORE 2.62

    DB:2.62:Delay Opening Cobol Application Over Network 9a


    I have a client who has a Cobol Application being used for their system. Their environment is 2x server 2008 R2 boxes and all clients are XP Pro SP3 workstations. There was a delay when on server 2003 r2 x64, but got worse after moving data to server 2008
    r2 (I had to move because main partition was messed up and didnt have license of media to reinstall svr2k3r2, so proceeded with svr2k8r2.)
    I need some help trying to figure this out. I have been working on this for a about 2 months with no resolution. I ran a packet capture and I do not see any network delay from the workstation side when opening the application up. But when sitting and watching
    the application, there is a 20-45 second delay vs running it off server taking 1s.

    Thanks for all the help. :)

    DB:2.62:Delay Opening Cobol Application Over Network 9a

    Hi,
    Please try to do the below suggestions:
    Suggestion 1: Please upgrade the NIC driver, and install the latest update on both Windows Server 2008 R2 and Clients.

    Suggestion 2: Run below command to disable the NIC chimney on Server 2008 R2.
    • netsh int tcp set global chimney=disabled

    • netsh int tcp set global rss=disabled

    • netsh int ip set global taskoffload=disabled

    • netsh int tcp set global autotuninglevel=disabled

    • netsh int tcp set global congestionprovider=none

    • netsh int tcp set global ecncapability=disabled

    • netsh int tcp set global timestamps=disabled
    Here is the detailed KB article. Hope it helps.
    Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008
    http://support.microsoft.com/kb/951037
    Best Regards,
    AidenAiden Cao
    TechNet Community Support

  • RELEVANCY SCORE 2.62

    DB:2.62:Tuxedo Cobol Conversation 7m


    Hi, people

    I'm new around here and I need help in some issue that I encountered in programming an ATMI COBOL application.

    I have the next application configuration: a COBOL server that runs into Tuxedo 8.1 and communicates with a Java client (applet) using the conversational communication model. The Weblogic platform is 8.1.
    When the client (the applet) tries to send data to the Tuxedo service the data doesn't reach to destination, i.e. the VIEW record that was sent to the client by the COBOL service doesn't contain the data that the client send it. Now, i saw a strange behavior due to the "TPRECV" operation on the COBOL server side: if I put a log operation immediately after the CALL "TPRECV".. line, the data sent by the client are filled up correctly into the VIEW COBOL record.

    This doesn't happen when I don't put the log operation mentioned above.

    It seams that the receiving operation on the server side does not wait to fill the data into the specified VIEW record.
    I've checked the flags that must be set for the TPRECV operation and everything seams to be OK, but i don't understand why the receiving operation works fine when has a log (USERLOG) operation immediately after it and it doesn't when the operation log is missing.
    The COBOL program that receives the data sent from the BEA side resides into a DLL file.
    Can this may be a problem? I don't think so.

    Many thanks

    Daniel

    DB:2.62:Tuxedo Cobol Conversation 7m

    Hi Todd

    The solution with resetting the record before his use with TPRECV is quite acceptable for the moment. I don't figure it out why this is necessary, but it seams to work.
    Instead, I need some answers on other questions that I asked on this forum and I didn't got the answer yet.

    Thank you

    Daniel

  • RELEVANCY SCORE 2.62

    DB:2.62:Cobol Formatted Output ff



    Is there a way to output an Informatica file containing a field that would correspond to a COBOL field defined as PIC S9(15)V99?

    For example, the Informatica output field is defined as number 19, 2 with a value of -2515.88. The COBOL program expects it to look like 0000000000025158Q where the last half byte contains the sign. Currently we have the COBOL program reading in the field as a string (PIC X(19)) and then converting it to a S9(15)v99 field. Just curious if there is some way to create this file on the Informatica side so the COBOL program can read in the numbers correctly?

    DB:2.62:Cobol Formatted Output ff


    Is there a way to output an Informatica file containing a field that would correspond to a COBOL field defined as PIC S9(15)V99?

    For example, the Informatica output field is defined as number 19, 2 with a value of -2515.88. The COBOL program expects it to look like 0000000000025158Q where the last half byte contains the sign. Currently we have the COBOL program reading in the field as a string (PIC X(19)) and then converting it to a S9(15)v99 field. Just curious if there is some way to create this file on the Informatica side so the COBOL program can read in the numbers correctly?

  • RELEVANCY SCORE 2.60

    DB:2.60:Art With Cobol-It f7


    Hi.

    I have a doubt with Tuxedo ART and Cobol-IT:

    i'm using Tuxedo ART Workbench to convert COBOL programs from z/OS COBOL to Cobol-IT. are these programs compatible with Tuxedo ART Runtime using Microfocus compiler instead of Cobol-IT compiler?

    Thanks.

    DB:2.60:Art With Cobol-It f7

    Hi,

    The COBOL programs converted by ART Workbench can be compiled using either COBOL-IT or Microfocus COBOL. When you use ART Workbench to convert COBOL programs from z/OS, it will generate "general" COBOL source programs, which are compatible with both COBOL-IT and Microfocus COBOL.

    Thanks,
    Sophia
    Tuxedo Dev

  • RELEVANCY SCORE 2.60

    DB:2.60:Compiling Cobol s8


    I tried compiling a sample cobol program (with embedded sql) with precompiler pro*COBOL for Oracle 8i. I used IBM visual Age for COBOl as the compiler. I was able to pre compile and compile the sample program provided with Oracle demo
    (precomp/demo/procob2) . I got the following linker error

    _SQLADR@8 could not resolve ..
    _SQLADRVC@12 """"
    _SQLBEX@0 etc...

    Could anyone help me in linking this.. I just have one library included (ORASQL8.lib)

    Thanks and Regards,
    Lal Praksh..

    DB:2.60:Compiling Cobol s8

    I tried compiling a sample cobol program (with embedded sql) with precompiler pro*COBOL for Oracle 8i. I used IBM visual Age for COBOl as the compiler. I was able to pre compile and compile the sample program provided with Oracle demo
    (precomp/demo/procob2) . I got the following linker error

    _SQLADR@8 could not resolve ..
    _SQLADRVC@12 """"
    _SQLBEX@0 etc...

    Could anyone help me in linking this.. I just have one library included (ORASQL8.lib)

    Thanks and Regards,
    Lal Praksh..

  • RELEVANCY SCORE 2.59

    DB:2.59:Migrating Forms 4.5 To Forms 10g jj


    Hi,

    I am migrating my forms 4.5 application on to forms 10g.
    Currently my oracle database 8i is installed on VMS server.
    Also, I am using call to COBOL and DCL functions written in my VMS server apart from database objects calls.

    I have query that when migrating to forms 10g, do I need to change the COBOL and DCL programs in PL/SQL and then call them from my forms or is there any method to call the COBOL and DCL programs through forms.

    Any help appreciated !!

    DB:2.59:Migrating Forms 4.5 To Forms 10g jj

    that's normally no problem.

    use client_host instead of host.

    You only need Webutil in this case to run the client_host. If you have installed Forms 10g Rel. 2, then your have installed webutil directly...

  • RELEVANCY SCORE 2.58

    DB:2.58:Please Somebody Help Me About Pro*Cobol With Linux-Suse 7.2 !!!!! c9


    Please somebody help me about Pro*Cobol !!!!

    I need create the runtime of Pro*Cobol for linux-suse 7.2, but when I created the rtsora, is very small and does not execute.Please , somebody help me !!!!

    DB:2.58:Please Somebody Help Me About Pro*Cobol With Linux-Suse 7.2 !!!!! c9

    Please somebody help me about Pro*Cobol !!!!

    I need create the runtime of Pro*Cobol for linux-suse 7.2, but when I created the rtsora, is very small and does not execute.Please , somebody help me !!!!

  • RELEVANCY SCORE 2.58

    DB:2.58:How To Access Oracle 10g With Cobol jz


    Hi there,

    I didn't find anywhere better to post this, so I'm sorry if this is the wrong place.

    I'm having major problems trying to find out how to access an Oracle 10g database with COBOL because I have no directions. I've never programmed anything that access a database before, and my first time must be in COBOL (wich is a language I started learning yesterday)

    My teacher (who is not a nice person) gave us no directions at all, and when we ask her for it she is rude
    "Do you know something called library? Or maybe, Google?"

    So I am here, desparate, asking for anyone's help, for any diirections.. like

    -How to access?
    -Wich COBOL compiler to use? (free)
    -Do I access the database with commands in COBOL? wich commands?
    -Any tutorial around the web about this?

    I have to deliver the full project in a month.. lol
    Oh well...
    thanks in advance!
    Oscar

    DB:2.58:How To Access Oracle 10g With Cobol jz

    Ozstrider, your posts do not even identify the platform you are working on but generally speaking if you look at the precomp library for the Oracle installation on your platform you should find sample programs and a compile script.

    You generally have to modify the script for the PATH to be used, that is, the location of the compiler, target directories, etc ....

    You should try the demo compile as is and see what happens. Based on the results you determine what if any changes you have to make. Talk to your classmates and find out what they are doing. Make sure you have not missed any fact like there is a set of compile instruction available in the computer lab, etc...

    This and the previous posts is about all the information I can provide.

    HTH -- Mark D Powell --

  • RELEVANCY SCORE 2.58

    DB:2.58:Calling Pro*Cobol From A Trigger 8m


    I want to call a cobol program when a record gets inserted into a table. This cobol program will check for certain conditions to determine what to do next. This cobol module has all the business rules. We have an external application inserting data directly into the table which is bypassing this module.

    Thanks

    DB:2.58:Calling Pro*Cobol From A Trigger 8m

    You could make the host call to the COBOL program from a Java stored procedure or an external (C) procedure - either of which would be called from the trigger.

  • RELEVANCY SCORE 2.58

    DB:2.58:How To Call A Cobol Function From Java? 1m


    Hi all,
    I have a Cobol application running on a Linux machine. The application takes in certain inputs from the user (from the Linux command prompt) and stores them within text files in its local directory. Again when the user enters a search keyword the Cobol looksup these files and retrieves the related information on a successful search. I dont have access to the text files but I have access to the application (I have the whole Cobol application coding available with me).

    My task is to develop a Java program that would interface with this Cobol application, call the Cobol functions that do the input/output with the text files and trap the necessary output.

    Can anybody suggest how to go about this. Had the coding been in C/C++ I would have thought of usingt Java Native Interface, but how to do it for Cobol?

    Thanks in advance.

    I am posting this everywhere to get attention. Sorry for the multiple posting.
    snodx

    DB:2.58:How To Call A Cobol Function From Java? 1m

    Try this for connection of Java with other programming languages:

    http://www.esus.com/javaindex/otherapis/javavarious/javavarious.html

    Cheers,
    Joris

  • RELEVANCY SCORE 2.58

    DB:2.58:How To Program In Cobol For Printers, Laserjet P1020 And P1606 With Different Fonts And Sizes Sheet 98



    Working with Open Cobol on Ubuntu. I have two printers LaseJet, P1020 and P1606dn. I want to print on different paper sizes, with different fonts and sizes, and different orientation (vertical and horizontal), this is possible from Cobol?If possible can anyone tell me how? from already thank you very much.

    DB:2.58:How To Program In Cobol For Printers, Laserjet P1020 And P1606 With Different Fonts And Sizes Sheet 98


    Working with Open Cobol on Ubuntu. I have two printers LaseJet, P1020 and P1606dn. I want to print on different paper sizes, with different fonts and sizes, and different orientation (vertical and horizontal), this is possible from Cobol?If possible can anyone tell me how? from already thank you very much.

  • RELEVANCY SCORE 2.58

    DB:2.58:Access To 10g From Z/Os z1


    I'm in the process of moving my DB2 database from z/OS to 10g on AIX. Now that the data is moved, I can't find any way to access the AIX/10g platfrom from my z/OS COBOL application. Does anyone know how to access AIX/10g from a z/OS COBOL application?

    DB:2.58:Access To 10g From Z/Os z1

    Thank you, but the Database Support link on this page doesn't say anything other than "Yes, you can." No other info in provided. Is there somewhere else I could look?

  • RELEVANCY SCORE 2.58

    DB:2.58:Issues With Cobol 17


    Hello All,We are impelmenting an upgrade of peoplesoft 9.1 to 9.2 peopletools 8.52 to 8.53. In the current version of PeopleSoft, our demo environment is hosted on a virtual image How do we get the COBOL install files transferred to this virtual image? Where can we find the cobol installation files?

    DB:2.58:Issues With Cobol 17

    See PeopleSoft Demo Images Home Page (Doc ID 1552548.1) "Note. If you want to run application functionality that requires COBOL object code, the COBOL source code needs to be compiled locally for Linux using your own license for the compiler."

  • RELEVANCY SCORE 2.58

    DB:2.58:Can Be Extracted Information From Cobol? pa


    is there any option to connect and extract information from COBOL under linux with QlikView?

    hay alguna opcin de conectar y extraer informacin de COBOL bajo linux con QlikView?

    DB:2.58:Can Be Extracted Information From Cobol? pa


    and this post is nice too...

    http://community.qlik.com/docs/DOC-2904#comment-4615

  • RELEVANCY SCORE 2.58

    DB:2.58:Problems Updating Mssql Date Field From 10g Using Dg4msql js


    Hi There,

    I have a strange consistency problems with the Transparent Gateway when connecting to Microsoft SQLServer

    We have successfully (for a number of years) been using OTG for connection our 10g database to a number of different verisons of MS SQL Databases.

    However 10g is going to end-of-life/support and we setup an test 11g gateway and started testing. All looks good, except we are unable to update a date field in the MS SQL database using our Cobol programs.

    If I perform the either of the following queries in sqlplus version 10g, I see in the trace file that the DATE is written as *"dob" = CONVERT (DATETIME, '1992-02-02 00:00:00')*

    update customer set "dob" = '02021992' where "customerNumber" = '10046014';
    update customer set "dob" = TO_DATE('02021992', 'ddmmyyyy') where "customerNumber" = '10046014';

    Hence the update works successfully.

    When the Cobol program runs (Microfocus and Oracle PreCompiler 10g) and performs the update with or without the TO_DATE function, there is no CONVERT (DATETIME (XXXX)) in the trace, but rather the generic *"dob" = ?* syntax.

    Hence the update is not working when we use the 11g gateway. It works, and has been working for years, successfully with 10g gateway.

    Any ideas?

    Viktor

    DB:2.58:Problems Updating Mssql Date Field From 10g Using Dg4msql js

    Hi Klaus,

    We already have a project in place to upgrade to 11g, and this involves upgrading the database and precompiler, as well as cobol, and all the testing and sign-off. If I was to upgrade to 10.2.0.5, it would divert some of our resources and delay the 11g upgrade.

    Now that I have a solution, I can put in a work around until we have the upgrade completed.

    -Viktor

  • RELEVANCY SCORE 2.58

    DB:2.58:Pre-Compilers za


    Hi all,
    Does anyone knows if oracle XE includes pre-compilers? I wanted to use cobol to write a program that accesses a XE database. I know that for the 10g enterprise edition, pro-cobol comes in the client CD. I believe i can't use this client with XE...

    Thank you

    DB:2.58:Pre-Compilers za

    Thank you.
    Well, i tried to install the 10g enterprise edition client on an linuux with a XE already installed but i get the following error:
    OUI-10133:Invalid staging area. There are no top level components for Linux for installation in this staging area.
    I tried with:
    ORACLE_BASE=/usr/lib/oracle and group name = dba (from XE installation)
    and with:
    ORACLE_BASE=/oracle and group name = oinstall (suggested in 10g client manual
    but i get the same error.
    do you have any idea what's going on?

    thanks again,
    Celio.

  • RELEVANCY SCORE 2.57

    DB:2.57:Perl And Pro*C From Oracle 9i To Oracle 10g kd


    Hi to all,
    on HP-UX 11 I have migrated form Oracle 9i to 10g R2 and I have some problems with Perl and pro*C scripts during connection to rdbms database.
    Shell I reinstall or migerate Perl and pro*C ?

    Is anybody there who can help me?

    DB:2.57:Perl And Pro*C From Oracle 9i To Oracle 10g kd


    ...I have some problems with Perl and pro*C scripts during connection to rdbms database.

    Pl provide complete details (along with any error messages) on the nature of the connection issues

    HTH
    Srini

  • RELEVANCY SCORE 2.57

    DB:2.57:Pro*Cobol V10.2.0.2.0 Ignores Option "Oreclen" On Openvms-Itanium jm


    We're migrating from OpenVMS-Alpha to Itanium and Oracle 9i to 10g in one step. (One of) My problem(s) is, that the Precompiler (V10) creates an Output that differs from Output of (9.2.0.5.0).
    The old Version has max recordlength to 80 Chars, the V10 Precompiler creates files with Records up to 256 Chars. The (unmodfied) default option "oreclen" is 80. I can define that option on command line, or system-default-file ora_pcc:pcbcfg.cfg with no result. The COBOL-Compiler doesn't accept that output.
    Any idea?
    Kay

    DB:2.57:Pro*Cobol V10.2.0.2.0 Ignores Option "Oreclen" On Openvms-Itanium jm

    The value you specify for IRECLEN should not exceed the value of ORECLEN. The maximum value allowed is system-dependent.

  • RELEVANCY SCORE 2.57

    DB:2.57:Pro*Cobol k1


    How can I get or download pro*cobol compiler for oracle 9 or 10?

    DB:2.57:Pro*Cobol k1

    How can I get or download pro*cobol compiler for oracle 9 or 10?