Sebastian Steinweg

We have taken a deeper look into the subject, including reviewing the implementation in COBOL-IT and the challenges involved in an older customer project, where the usage of BIT was extremely complex and risky( usage of up to PIC 1(32767)!!!). We have been able to identify the major steps that would be necessary to implement this requirement, and see some distinct activities required. Full implementation of Usage Bit behaviour in the data definition including behaviour in complex structures like...

Your change suggestion is correct in our view. It's always "minus 0x10". The problem is the reference to the documentation. The topic belongs to a migration project in the past from CA Realia to another compiler, were the display of sign seperate was a topic, that should be implemented. The change in that project was done by the compiler manufacturer and we did not have a CA Realia documentation in physical form. We found one online, but there are two things. It is written in old Windows help form...

Your change suggestion is correct in our view. It's always "minus 0x10". The problem is the reference to the documentation. The topic belongs to a migration project in the past from CA Realia to another compiler, were the display of sign seperate was a topic, that should be implemented. The change in that project was done by the compiler manufacturer and we did not have a CA Realia documentation in physical form. We found one online, but there are two things. It is written in old Windows help form...

Hello Vincent, The issue is working with Faircom c-tree and not BerkleyDB. c-tree works correctly with Micro Focus, Acucobol, RM/COBOL, COBOL-IT and NETCOBOL. However not with GnuCOBOL. The engineers at Faircom have informed us that the problem lies in the incorrect implementation of EXTFH. It is of course possible that it works with ISAM and perhaps the implementation of BerkleyDB is such that it is not dependent on the EXTFH. Any file system that is expecting the documented EXTFH behaviour will...

There occurs an error during the make process numeric.c:1875:34: error: ‘COB_FERROR_DIV_ZERO’ undeclared (first use in this function); did you mean ‘COB_FERROR_FILE’? 1875 | cob_fatal_error (COB_FERROR_DIV_ZERO); | ^~~~~~~~~~~~~~~~~~~ There is no definition of COB_FERROR_DIV_ZERO in the common.h where all other COB_FERROR* was defined And also no usage of this constant anywhere grep -R COB_FERROR_DIV_ZERO * libcob/numeric.c: cob_fatal_error (COB_FERROR_DIV_ZERO); libcob/intrinsic.c: cob_fatal_error...

Thanks you for your response. ok, as I wrote ROLLBACK and COMMIT is maybe not fully implemented or not implemented the way we expected. In our view this is one topic. The other topic is REWRITE and DELETE, which should work as well with any other EXTFH.

wrong data behaviour with GnuCOBOL & c-tree DB via EXTFH

Hi, could you please send me a link to download the latest version of GC 4.x. I'm not sure, but it seems that the links in the download area are not working.