Hi Laura, > Date: Fri, 4 May 2018 14:35:12 -0400 > From: LM <lmemsm@xxxxxxxxx> > On Fri, May 4, 2018 at 11:30 AM, Ron Norman <rjn@xxxxxxxxxxxx> wrote: >> VB-ISAM works fine... Make sure you have the 2.1.1 version or later. >> Install or build VB-ISAM and then rebuild the GnuCOBOL compiler to use that. Actually the best way to test an installed VBISAM version is to run `make checkall` (= running both the internal and the NIST test suite) after `configure --with-vbisam && make`. Note: not all versions will have a full feature set but all versions later than 2.0 should pass both testsuites. If you change code within VBISAM you likely want to do `make` in VBISAM's "tests" subdirectory. Note: if you do any changes in VBISAM it is likely best to do `make clean` there before re-running the tests after a change. In general you should be able to use any program for testing C-ISAM (though I'm not sure if you find more there). > > Where did you find the source code for 2.1.1? > > Sourceforge has 2.0 ( https://sourceforge.net/projects/vbisam/files/vbisam2/ ). > I also found vbisam 2.0.1 ( http://www.arnoldtrembley.com/GnuCOBOL.htm ) Ron adjusted the official VBISAM 2.0 sources, mainly for supporting DUPS (returning the correct status on a duplicate secondary key) and for SPARSE KEY support after discussing these items with me. He sent all the sources and I try to get them on the official site within the next two months. Simon
