[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20040217: gdbm file reader program

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20040217: gdbm file reader program
  • Date: Tue, 17 Feb 2004 10:26:16 -0700
Neil,

>Date: 13 Feb 2004 17:27:24 -0600
>From: "Neil R. Smith" <address@hidden>
>Organization: TAMU
>To: Steve Emmerson <address@hidden>
>Subject: Re: 20040213: gdbm file reader program
>Keywords: 200401280025.i0S0PCp2028769 LDM gdbm

The above message contained the following:

> OK. I finally got success with this code reading platform-
> native db files with the following change:
> 
>         station.dptr = "KCLL";
>         station.dsize = (int) strlen(station.dptr) +1;
> 
> So the data key is the WMO station code and its string 
> lenth should be greater by one. I got this from the LDM's
> pqact filel.c code.
> 
> So now I have a program that executes gdbm_fetch successfully
> on platform-native gdbm files.
> 
> What might be platform-dependent about the db files that doesn't
> show up as a problem with other binary files like the model
> data grib files or gempak-decoded model files?

I'm afraid that I don't know enough about GDBM to answer your question.

I do wish you good luck.

Perhaps there's a GDBM mailing-list or forum?

Regards,
Steve Emmerson