Artie A

Simon how do I get access to re-branch?

Thanks so much for doing the test. What version of VBISAM are you using?? 2.0.1 I made the same changes to file-status and record size but it still failed on my PC. I guess it is a win 10/cobc problem with VBISAM. A little history. I am converting an POS/AR package written MF DOS cobol 16bit from 1993 to run on win10 PCs. OC using BDB works except for 2 problems. The locking msg problem which I got around by not doing unlocks but close the file then re-opening and use a START to get back where I...

Thanks for testing it on Linux. I put in your changes and I still get the error msg BDB2056 DB_LOCK->lock_put: Lock is no longer valid. I think it is a problem with running cobc & BDB on a win 10 32bit PC. I reported bug 534 get sigsegv fault on a READ NEXT using VBISAM. The program runs fine with BDB Could do me a big favor and test bug 534 on your Linux box if possible. I get this TESTVSAM.CBl: 282: attempt to reference unallocated memory (signal SIGSEGV) libcob: TESTVSAM.CBl:282: warning: implicit...

I did more testing using REWRITE WITH LOCK and it failed too when I do the CLOSE. Currently my programs do not do any UNLOCK statements. After 100 locks are done I close the file and re-open and do a START at the last record that was re-written. Here is a new version of the program that fails.

Thanks for looking at it so quickly. I do run with a few environment flags set. DB_HOME is one I set to my ISAM data folder. The OC manual says you must have this set for locks to work. I am using the same BDB version as Arnold ISAM handler : BDB, version 6.232 I would leave the return status as "00". You are correct that the msg is display when you close the file if you did a unlock statement when no locks were active. My old MF 1993 compiler didn't have "REWRITE "with LOCK option " but would keep...

I have attached the BDBLOCK test program. Just compile it and run. It deletes the isam file first then builds it with 2 records. Then it closes the file open, locks the first record. Next it does a rewrite on the record without lock. Which causes the BDB2056 DB_LOCK->lock_put on errout device when i do the UNLOCK. OC should throw away the error msg like VBISAM does since I am trying to remove locks anway. The BDB version is the one that Arnold built for GCR3.0 C:\POS\psale>db_stat -d BDBISAM Fri...

cobc got sigsegv fault when FD name missing in SELECT statement

Thanks for your good eyesight. Line 183 should be DISPLAY "OK" AT 0530. I am willing to help in anyway. Is there a quick way to turn on VBISAM debug and a C trace through OC fileio.c The strange thing with VBISAM is the .IDX file has the data and the keys are in the .DAT Artie From: Simon Sobisch Sent: Thursday, June 28, 2018 6:40 AM To: [open-cobol:bugs] Subject: [open-cobol:bugs] Re: #531 Open extend has errors Hi Artie, thank you for all the tickets with reasonable test sources you created against...