Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Vendor-Defined Status Key 2 Meaning for OpenCobol Error

Anonymous
2014-07-18
2014-08-01
1 2 > >> (Page 1 of 2)

  • Anonymous
    2014-07-18

    Hi Team,

    In the output below, what is the error being referenced by the FILE-STATUS-KEY-2 of "049"?

    Thanks,
    Susanne


    Creating lookup table...
    sccrs_seek_monthly Cleaning file /tmp/sccrs_seek_monthly_LOOKUP_TBL_SQL_12280.out.ascii...

    sccrs_seek_monthly Starting execution of SK060000 transformation on 20140716...

    WARNING - Implicit CLOSE of WFINPUT2-FILE ("SK060WFINPUT2")
    WARNING - Implicit CLOSE of WFINPUT-FILE ("SK060WFINPUT")
    sccrs_seek_monthly PROBLEMS - Refer to /tmp/sccrs_seek_monthly_ERROR_LOG_12280 for details

    sccrs_seek_monthly Sending notification...

    Temp file referred to above in nohup.out looks as follows:
    s032:/usr/DATA/ETL/reports> cat sccrs_seek_monthly.sysout
    Error Opening File: SK060100
    File Status Return Code FILE-STATUS-KEY-1: 9 FILE-STATUS-KEY-2: 049 <<<<<<<<<<<<<<<<< MEANING????

    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    SK060000 ABENDED WITH A RETURN-CODE OF 91
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

     
  • Simon Sobisch
    Simon Sobisch
    2014-07-18

    Depends on how you've got file-status-key-1 and file-status-key-2. Posting this necessary information will help to get the answer.

    Simon

     
  • I have a login now.

    Here is what I posted earlier for the moderator...

    My customer, Tony, Cobol programmer, responded...

    Here is the code that I think they are looking for:

    *>File control definition…
           FILE-CONTROL.
          *>    ISAM File Of County Data (060T)
               SELECT SK060100-FILE
                   FILE STATUS IS FILE-STATUS
                   ASSIGN TO "SK060100"
                   ORGANIZATION IS INDEXED
                   ACCESS MODE IS SEQUENTIAL
                   RECORD KEY IS COUNTY-NUMBER
                       OF SK060100-REC.
    
    *>Working storage area…
               05  FILE-STATUS                  PIC X(02).
                   88  FILE-STATUS-OK                      VALUE '00'.
                   88  FILE-ATTRIB-ERR-READ                VALUE '04'.
                   88  FILE-END-OF-FILE                    VALUE '10'.
                   88  FILE-STATUS-OUT-OF-SPACE            VALUE '34'.
                   88  FILE-NOT-FOUND                      VALUE '35'.
                   88  FILE-ATTRIB-MISMATCH                VALUE '39'.
                   88  FILE-SEQ-READ-ERROR                 VALUE '46'.
                   88  FILE-NOT-OPEN-READ-ERROR            VALUE '47'.
                   88  FILE-SLACK-BYTE                     VALUE '9 '.
    
               05  FILLER REDEFINES FILE-STATUS.
                   10  FILE-STATUS-KEY-1        PIC X.
                   10  FILE-STATUS-KEY-2        PIC 9(02) COMP-X.
                   10  FILE-STATUS-KEY-2        PIC 9(02) COMP-3.
    
    *>Open statement and display of status…
               OPEN OUTPUT SK060100-FILE.
               IF  NOT FILE-STATUS-OK
                   DISPLAY 'Error Opening File:  SK060100'
                   IF  FILE-STATUS-KEY-1 EQUALS '9'
                       DISPLAY 'File Status Return Code '
                               'FILE-STATUS-KEY-1: ' FILE-STATUS-KEY-1 ' '
                               'FILE-STATUS-KEY-2: ' FILE-STATUS-KEY-2
                   ELSE
                       DISPLAY 'File Status Return Code: ' FILE-STATUS
                   END-IF
                   MOVE FILE-STATUS             TO WFABEND-CODE
                   PERFORM S999-ABEND
               END-IF.
    

    We are using Berkeley DB, V4.7, but this can change if needed.

    Regards,
    Susanne, OS Admin

     
    Last edit: Simon Sobisch 2014-07-21
    • Luke Smith
      Luke Smith
      2014-07-21

      These code snips can't compile. It has FILE-STATUS-KEY-2 defined twice.

      But aside from that, what this code shows is a technique common to Micro Focus. Whenever they get a "9x" file status code, the x is a 1 byte binary number. That way they can have up to 255 different "9x" error codes. Look in their manual for the list.

      GNU COBOL doesn't have any binary numbers in the file status codes. So this code isn't useful for this compiler.

      Convert the x into a display number to print it. The DISPLAY statement in the code did the conversion automatically, but I wouldn't count on it on all compilers.

      In this case it converted to a number 049. Looking up that number in the ASCII table shows that it is character "1".

      So the file status code in question is "91". We can see that as the last display from S999-ABEND.

      All "9x" codes are vendor defined. To determine what this means, you must look in the manual for the vendor. If this Micro Focus, you must look in their book. The GNU COBOL manual can't help with that.

      But if this is being run with GNU COBOL, the GNU COBOL manual shows "91" as meaning "File not available."

      Again, if this is not being run with GNU COBOL, then "91" might mean something completely different.

       
  • Hi,

    you can see all FILE-STATUS codes in the Doc.: GNU COBOL 2.0 Programmer’s Guide.
    But your re-definition does not match with the Document:

    "The FILE STATUS or SORT STATUS clause (they are both equivalent and only one or the other, if any, should be specified) is used to specify the name of a PIC 9(2) data item into which an I/O status code will be saved after every I/O verb that is executed against the file. This does not actually allocate the data item – you still need to allocate the item yourself somewhere in the DATA DIVISION."

    It must be also PIC 9(2), and then you can use for example this code to get a message:

     ENVIRONMENT DIVISION.
     INPUT-OUTPUT SECTION.
     FILE-CONTROL.
        SELECT COB-FILE ASSIGN             TO WS-COB-FILE-NAME
               STATUS                      IS WS-COB-FILE-STATUS
               ORGANIZATION                IS LINE SEQUENTIAL.
    
     DATA DIVISION.
     FILE SECTION.
     FD COB-FILE.
     01 COB-LINE                           PIC X(4096).
    
     WORKING-STORAGE SECTION.
    
    *> file-status
     01 WS-FILE-STATUS.
       02 WS-COB-FILE-STATUS               PIC 9(02).
          88 V-COB-FILE-OK                 VALUE 00.
          88 V-COB-FILE-EOF                VALUE 10.
    
    *> file-status message
     01 WS-FS-MESSAGE.
       02 FILLER                           PIC X(13) VALUE "Status Code: ".
       02 WS-FS-CODE                       PIC 9(2).
       02 FILLER                           PIC X(11) VALUE ", Meaning: ".
       02 WS-FS-MSG-TXT                    PIC X(25).  
    
     PROCEDURE DIVISION.
    
     DECLARATIVES.
    
    *>---------------------------------------------------------------------- 
     COB-FILE-ERROR SECTION.
    *>---------------------------------------------------------------------- 
    
        USE AFTER STANDARD ERROR PROCEDURE ON COB-FILE.
    
        IF NOT V-COB-FILE-EOF OF WS-COB-FILE-STATUS
        THEN
           MOVE WS-COB-FILE-STATUS 
             TO WS-FS-CODE                 OF WS-FS-MESSAGE
           PERFORM EVAL-FILE-STATUS  
           DISPLAY WS-FS-MESSAGE
        END-IF
    
        EXIT SECTION
    
        .
     COB-FILE-ERROR-EX.
        EXIT.
    
    *>---------------------------------------------------------------------- 
     EVAL-FILE-STATUS SECTION.
    *>---------------------------------------------------------------------- 
    
        EVALUATE WS-FS-CODE OF WS-FS-MESSAGE
           WHEN 00 MOVE "SUCCESS "                 TO WS-FS-MSG-TXT
           WHEN 02 MOVE "SUCCESS DUPLICATE "       TO WS-FS-MSG-TXT
           WHEN 04 MOVE "SUCCESS INCOMPLETE "      TO WS-FS-MSG-TXT
           WHEN 05 MOVE "SUCCESS OPTIONAL "        TO WS-FS-MSG-TXT
           WHEN 07 MOVE "SUCCESS NO UNIT "         TO WS-FS-MSG-TXT
           WHEN 10 MOVE "END OF FILE "             TO WS-FS-MSG-TXT
           WHEN 14 MOVE "OUT OF KEY RANGE "        TO WS-FS-MSG-TXT
           WHEN 21 MOVE "KEY INVALID "             TO WS-FS-MSG-TXT
           WHEN 22 MOVE "KEY EXISTS "              TO WS-FS-MSG-TXT
           WHEN 23 MOVE "KEY NOT EXISTS "          TO WS-FS-MSG-TXT
           WHEN 30 MOVE "PERMANENT ERROR "         TO WS-FS-MSG-TXT
           WHEN 31 MOVE "INCONSISTENT FILENAME "   TO WS-FS-MSG-TXT
           WHEN 34 MOVE "BOUNDARY VIOLATION "      TO WS-FS-MSG-TXT
           WHEN 35 MOVE "FILE NOT FOUND "          TO WS-FS-MSG-TXT
           WHEN 37 MOVE "PERMISSION DENIED "       TO WS-FS-MSG-TXT
           WHEN 38 MOVE "CLOSED WITH LOCK "        TO WS-FS-MSG-TXT
           WHEN 39 MOVE "CONFLICT ATTRIBUTE "      TO WS-FS-MSG-TXT
           WHEN 41 MOVE "ALREADY OPEN "            TO WS-FS-MSG-TXT
           WHEN 42 MOVE "NOT OPEN "                TO WS-FS-MSG-TXT
           WHEN 43 MOVE "READ NOT DONE "           TO WS-FS-MSG-TXT
           WHEN 44 MOVE "RECORD OVERFLOW "         TO WS-FS-MSG-TXT
           WHEN 46 MOVE "READ ERROR "              TO WS-FS-MSG-TXT
           WHEN 47 MOVE "INPUT DENIED "            TO WS-FS-MSG-TXT
           WHEN 48 MOVE "OUTPUT DENIED "           TO WS-FS-MSG-TXT
           WHEN 49 MOVE "I/O DENIED "              TO WS-FS-MSG-TXT
           WHEN 51 MOVE "RECORD LOCKED "           TO WS-FS-MSG-TXT
           WHEN 52 MOVE "END-OF-PAGE "             TO WS-FS-MSG-TXT
           WHEN 57 MOVE "I/O LINAGE "              TO WS-FS-MSG-TXT
           WHEN 61 MOVE "FILE SHARING FAILURE "    TO WS-FS-MSG-TXT
           WHEN 91 MOVE "FILE NOT AVAILABLE "      TO WS-FS-MSG-TXT
        END-EVALUATE
    
        .
     EVAL-FILE-STATUS-EX.
        EXIT.            
    
     END DECLARATIVES.
    

    László

     
    Last edit: Simon Sobisch 2014-07-21
    • Brian Tiffin
      Brian Tiffin
      2014-07-22

      Nice, László

      But, 91 isn't FILE NOT AVAILABLE, it's FEATURE NOT AVAILABLE. Compile time options and choice of ISAM engine can trigger this. Just in case you ever actually see that status and need to start digging in.

      If a custom EXTFH doesn't support delete, then DELETE FILE can return a 91, for instance. (EXTFH being one of the ./configure --with-index-extfh=... advanced compiler build options. There are other custom configurations that can trip a 91.)

      Cheers,
      Brian

       
      • Hi Brian,

        there is a table about it, in GNU COBOL 2.0 Programmers Guide, page 4-11. We have to change the message for 91 there.

        László

         
  • Tony Partin
    Tony Partin
    2014-07-21

    Hi, I'm Tony the programmer...
    I've modified the code just slightly to make it easier to understand what is going on. No functionality changed and results are the same.

    File control looks as follows:

           *    ISAM File Of County Data (060T)
           *********
                SELECT SK060100-FILE
                    FILE STATUS IS FILE-STATUS
     ##GNU#         ASSIGN TO "SK060100"
                    ORGANIZATION IS INDEXED
                    ACCESS MODE IS SEQUENTIAL
                    RECORD KEY IS COUNTY-NUMBER
                        OF SK060100-REC.
    

    Working storage looks as follows:
    You'll notice the last line is commented out which was included in the original post & I changed FILE-STATUS from X(02) to 9(02).

            01  WFCOMMON-WS-AREA.
     ##GNU#     05  FILE-STATUS                  PIC 9(02). 
                    88  FILE-STATUS-OK                      VALUE '00'.
                    88  FILE-ATTRIB-ERR-READ                VALUE '04'.
                    88  FILE-END-OF-FILE                    VALUE '10'.
                    88  FILE-STATUS-OUT-OF-SPACE            VALUE '34'.
                    88  FILE-NOT-FOUND                      VALUE '35'.
                    88  FILE-ATTRIB-MISMATCH                VALUE '39'.
                    88  FILE-SEQ-READ-ERROR                 VALUE '46'.
                    88  FILE-NOT-OPEN-READ-ERROR            VALUE '47'.
                    88  FILE-SLACK-BYTE                     VALUE '9 '.
    
                05  FILLER REDEFINES FILE-STATUS.
                    10  FILE-STATUS-KEY-1        PIC X.
     ##075#         10  FILE-STATUS-KEY-2        PIC 9(02) COMP-X.
     ##075#*        10  FILE-STATUS-KEY-2        PIC 9(02) COMP-3.
    

    And I made some small changes to the displays that where causing confusion among the various people looking at this.
    Following is the code that opens an ISAM file for output that is generating the error. This is being run with GNU COBOL (we are trying to convert our system from MicroFocus COBOL) and I understand the KEY-1 & KEY-2 fields are not useful at this time but are just leftover from running MF.

            OPEN OUTPUT SK060100-FILE.
            IF  NOT FILE-STATUS-OK
                DISPLAY 'Error Opening File:  SK060100'
                IF  FILE-STATUS-KEY-1 EQUALS '9'
                    DISPLAY 'File Status Return Code '
                    DISPLAY 'FILE-STATUS      : ' FILE-STATUS ' '
                    DISPLAY 'FILE-STATUS-KEY-1: ' FILE-STATUS-KEY-1 ' '
                    DISPLAY 'FILE-STATUS-KEY-2: ' FILE-STATUS-KEY-2
                ELSE
                    DISPLAY 'File Status Return Code: ' FILE-STATUS
                END-IF
                MOVE FILE-STATUS             TO WFABEND-CODE
                PERFORM S999-ABEND
            END-IF.
    

    And finally this is what the modified displays look like.

    Error Opening File:  SK060100
    File Status Return Code
    FILE-STATUS      : 91
    FILE-STATUS-KEY-1: 9
    FILE-STATUS-KEY-2: 049
    
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    SK060000 ABENDED  WITH A RETURN-CODE OF 91
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    

    Thanks for all the help!

     
    Last edit: Simon Sobisch 2014-07-21
  • Tony Partin
    Tony Partin
    2014-07-21

    Also we are running GNU COBOL 1.1.

     
    • Simon Sobisch
      Simon Sobisch
      2014-07-21

      Please include the output from cobc --info (or cobc --version if the first command is not implemented).

       
  • Simon Sobisch
    Simon Sobisch
    2014-07-21

    Having a quick look at 1.1:

    case COB_STATUS_91_NOT_AVAILABLE:
        msg = "Runtime library is not configured for this operation";
    

    This should be only returned if you configured --without-db. But the output of cobc --info will shed some light on this.

    Simon

     
  • Jumping in here, given that I did the install. I chose with-db, but specified that I wanted a particular version. Here it is:

      umask 022
      ./configure --with-db=/usr/local/BerkeleyDB.4.7 --without-libiconv-prefix -C
    

    Also,

    root@s032:[95] cd /usr/local/bin
    root@s032:[96] ./cobc --info
    cobc (GNU Cobol) 1.1.0
    Copyright (C) 2001,2002,2003,2004,2005,2006,2007 Keisuke Nishida
    Copyright (C) 2006-2012 Roger While
    This is free software; see the source for copying conditions.  There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    Built     Jun 26 2014 13:02:32
    Packaged  Jan 20 2014 07:40:53 UTC
    C version "3.4.6"
    Build information
    Build environment        : sparc-sun-solaris2.10
    CC                       : /usr/local/bin/gcc -m64
    CPPFLAGS                 : -m64 -I/usr/local/BerkeleyDB.4.7/include
                               -I/usr/local/include -I/usr/local/share
    CFLAGS                   : -m64 -I/usr/local/BerkeleyDB.4.7/include
                               -I/usr/local/include -I/usr/local/share
                               -finline-functions -fsigned-char -Wall
                               -Wwrite-strings -Wmissing-prototypes
                               -Wno-format-y2k
    LD                       : ld
    LDFLAGS                  : -m64 -L/usr/local/lib/sparcv9
                               -L/usr/local/lib
                               -L/usr/local/BerkeleyDB.4.7/lib
                               -L/usr/local/share
    
    GNU Cobol information
    COB_CC                   : /usr/local/bin/gcc -m64
    COB_CFLAGS               : -I/usr/local/include -m64
                               -I/usr/local/BerkeleyDB.4.7/include
                               -I/usr/local/include -I/usr/local/share -m64
                               -I/usr/local/BerkeleyDB.4.7/include
                               -I/usr/local/include -I/usr/local/share
    COB_LDFLAGS              : -m64 -L/usr/local/lib/sparcv9
                               -L/usr/local/lib
                               -L/usr/local/BerkeleyDB.4.7/lib
                               -L/usr/local/share
    COB_LIBS                 : -m64 -L/usr/local/lib/sparcv9
                               -L/usr/local/lib
                               -L/usr/local/BerkeleyDB.4.7/lib
                               -L/usr/local/share -L/usr/local/lib -lcob -lm
                               -lgmp -lrt -lcurses
    COB_CONFIG_DIR           : /usr/local/share/gnu-cobol/config
    COB_COPY_DIR             : /usr/local/share/gnu-cobol/copy
    COB_LIBRARY_PATH         : /usr/local/lib/gnu-cobol
    COB_MODULE_EXT           : so
    COB_EXEEXT               :
    Dynamic loading          : System
    "CBL_" param check       : Disabled
    Variable format          : 0
    BINARY-C-LONG            : 8 bytes
    Sequential handler       : Internal
    
     
    Last edit: Simon Sobisch 2014-07-21
    • Simon Sobisch
      Simon Sobisch
      2014-07-21

      Looks valid.

      The temporary fix for 1.1 is likely to change config.h, these two must be set in your case

      /* Use Berkeley DB library new features */
      #define USE_DB41 1
      
      /* Compile with the Berkeley DB library */
      #define WITH_DB 3
      

      and do make && make check && make check again.

      Can you please recheck with 2.0 from svn (adding --prefix=whereeveryouwantto)? Even if this means you have to recompile the COBOL sources too, if there is the need for a bugfix it will likely be placed in 2.0.

      Simon

       
  • When I look in config.h, it appears that the option "--with-db=/usr/local/BerkeleyDB.4.7" did not really work on the configure statement. I mean, this is what I am seeing:

    / Use Berkeley DB library new features /
    / #undef USE_DB41 /

    / Compile with the Berkeley DB library /
    / #undef WITH_DB /

    So, perhaps the issue I had with errors related to BerkeleyDB.4.7 vs SUNWbdb (BerkeleyDB-Base 4.2.52 also installed) was not really resolved when I tried that. I never noticed a problem when I ran the checks.

    In any event, will your workaround resolve this? If I remember correctly, there was an issue with not being able to find Berkeley DB 4.7 during the configure or make.

     
    • If I may make a comment with only seeing some of the posts:

      Status code is pic 99 or if you have a need xx.

      It is not split into binary.
      However for a MF compiler that is valid but NOT GNU / Open Cobol.

      Please see the programmers manual/guide.

      Vince

       
      Last edit: Simon Sobisch 2014-07-21
    • Simon Sobisch
      Simon Sobisch
      2014-07-21

      I'd try to reconfigure first:

      LD_LIBRARY_PATH=/usr/local/BerkeleyDB.4.7/lib
      export LD_LIBRARY_PATH
      ./configure CXXFLAGS=-I/usr/local/BerkeleyDB.4.7/include LDFLAGS=-L/usr/local/BerkeleyDB.4.7/lib --without-libiconv-prefix
      

      If this doesn't work (see summary at end of configure) you could try to change the config.h entries as mentioned above and try a make afterwards (you either can compile it or not).
      In any case make check should work fine, with no skipped tests (only ISAM related tests are skipped in 1.1 if no ISAM is configured).

      If this doesn't work try 2.0-branch (with the configure line above), the configure+make scripts were changed a lot (make check in 2.0-branch will currently skip report-writer tests).

      Simon

       
  • I am getting ready to run this now, but noticed that the configure statement above does not include "--with-db". Did you mean to say:

    export LD_LIBRARY_PATH=/usr/local/BerkeleyDB.4.7/lib

    ./configure CXXFLAGS=-I/usr/local/BerkeleyDB.4.7/ \ include LDFLAGS=-L/usr/local/BerkeleyDB.4.7/lib \ --with-db --without-libiconv-prefix

     
    • Simon Sobisch
      Simon Sobisch
      2014-07-22

      There is (currently) no need to add --with-db as this is the standard option. I'd change the export to

      export LD_LIBRARY_PATH=/usr/local/BerkeleyDB.4.7/lib:$LD_LIBRARY_PATH
      

      Simon

       
  • Fixed typos in question above about with-db:

    ./configure CXXFLAGS=-I/usr/local/BerkeleyDB.4.7/include LDFLAGS=-L/usr/local/BerkeleyDB.4.7/lib --with-db --without-libiconv-prefix

     
  • Same results both ways. Back to my original error from a month ago. The configure tries to find the version and is unable to do so. Bug? Does not like BerkeleyDB version 4.7

    So, I guess I need to run it the way it works, then edit the config.h, correct gurus?

    root@scc032: ./configure CXXFLAGS=-I/usr/local/BerkeleyDB.4.7/include LDFLAGS=-L/usr/local/BerkeleyDB.4.7/lib --without-libiconv-prefix
    checking for a BSD-compatible install... ./install-sh -c
    checking whether build environment is sane... yes
    (snip)
    checking for Berkeley DB db.h version >= 4.1 ... yes (4.7)
    configure: error: Include file db.h implies version >=4.1 but no library found

     
    • May have come up before but:

      What DB47 libraries have you installed?
      Have you installed : lib64db4.7 and lib64db4.7-devel

      or if you only use 32 bit Linux same as above but without the '64' bit.

      Vince

       
      Last edit: Simon Sobisch 2014-07-22
    • Simon Sobisch
      Simon Sobisch
      2014-07-22

      As said before: GNU Cobol 2.0 will work - as it uses the extracted version number (in your case 4.7) for checking the correct library.

      You can kind-of-fix 1.1 (both configure.ac [just in case you regenerate it] and configure)

      @@ -435,3 +435,3 @@
              export MYOCLIBS
      -       for MYOCLIBS in db db-4.5 db-4.4 db-4.3 db-4.2 db-4.1
      +       for MYOCLIBS in db db-4.7 db-4.6 db-4.5 db-4.4 db-4.3 db-4.2 db-4.1
              do
      

      configure should find the correct library afterwards.

      Simon

       
      • Tony Partin
        Tony Partin
        2014-07-23

        We are new to OpenCobol/GNU Cobol but experienced with COBOL. We don't know whether to stay with COBOL 1.1 or move to COBOL 2.0. Our usage is strictly batch processing of files. We are a Data Warehouse using COBOL to perform the extract and transform tasks of Extract, Transform and Load (ETL). There is no transactional or interactive or visual aspect to our usage.

        With all the caveats about not being a "stable release" should we consider using COBOL 2.0 considering it is the now the more supported and patched version?

         
        • It has been stable for me over the last 2-3 years with very few bugs
          seen but there again I just put my some 100+ programs through it and if
          they work I am happy.

          I have used many of the functions that are in v2 but not some of the
          more weird one's.

          Would I recommend it : Yes at least try it and run a test batch flow
          through but not sure you will notice much in speed throughput but it is
          a lot cleaner.

          My current one and has been for all of this year is v2.1 with report
          writer under Linux X64.

          Vincent

          On 23/07/14 13:13, Tony Partin wrote:

          We are new to OpenCobol/GNU Cobol but experienced with COBOL. We don't
          know whether to stay with COBOL 1.1 or move to COBOL 2.0. Our usage is
          strictly batch processing of files. We are a Data Warehouse using
          COBOL to perform the extract and transform tasks of Extract, Transform
          and Load (ETL). There is no transactional or interactive or visual
          aspect to our usage.

          With all the caveats about not being a "stable release" should we
          consider using COBOL 2.0 considering it is the now the more supported
          and patched version?


          Vendor-Defined Status Key 2 Meaning for OpenCobol Error
          https://sourceforge.net/p/open-cobol/discussion/help/thread/a05baee7/?limit=25#eaec/92f0/861d


           
1 2 > >> (Page 1 of 2)


Anonymous


Cancel   Add attachments