[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-GnuCOBOL] FW: ISAM unhappy
From: |
Graham Robbins |
Subject: |
[Bug-GnuCOBOL] FW: ISAM unhappy |
Date: |
Fri, 12 Jan 2018 16:06:01 +0000 |
- GNU Cobol -
Please could you remove Joe Robbins address@hidden from your distribution list.
Joe died last year.
Thank you.
Best Regards
Graham Robbins
Director, John Hudson Trailers
Europe’s Largest Hire Fleet of Specialised Trailers
BAWTRY, Doncaster, DN10 6NX, UK
e address@hidden | w www.johnhudson.co.uk
m +44 (0)7720 509 683 | t +44 (0)1302 710 711
reg 122 12 49 | vat GB 182 629 347 | tva FR 72 490 887 726 | moms SE 502 078
196 801
-----Original Message-----
From: Bug-GnuCOBOL [mailto:address@hidden On Behalf Of Ron Norman
Sent: 12 January 2018 15:01
To: James K. Lowden <address@hidden>
Cc: address@hidden
Subject: Re: [Bug-GnuCOBOL] ISAM unhappy
I checked the code and that status 91 and message could happen if GnuCOBOL was
configured with NO ISAM handler at all.
I do not think it defaults to BDB and you likely have to select that.
It looks like it defaults to NO ISAM handler.
On Thu, Jan 11, 2018 at 7:14 PM, James K. Lowden <address@hidden
<mailto:address@hidden> > wrote:
Hi all,
I'm having trouble testing ISAM support with the default Berkeley DB
implementation:
libcob: IX101A.CBL: 399: runtime library is not configured for
this operation (status = 91) file: 'XXXXX024'
The compiler was built from the distribution tarball:
$ sed -ne 4,17p config.log
It was created by GnuCOBOL configure 2.2, which was
generated by GNU Autoconf 2.69. Invocation command line was
$ ../configure
## --------- ##
## Platform. ##
## --------- ##
hostname = lts16
uname -m = x86_64
uname -r = 4.4.0-98-generic
uname -s = Linux
uname -v = #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017
i have not yet determined where in libcob this message comes from, or
why the system thinks there's no ISAM support.
I'm also not sure which libcob produces the message. I would like to
think it's the one that was installed when the compiler was installed
(same sources) but perhaps the test programs are built to use the
not-yet-installed library in the source tree?
Regards,
--jkl
--
Cheers
Ron Norman