Re: Journal APIs

Thanks to all for the info. Carsten's example set me straight. I wrote a
test peice that uses an auto-extending user space, and stores all file
actions, then walks a DS through these actions for storage in a DB file. I
speed-tested it and compared to using DSPJRN to an outfile, and reading
through it, it FLIES!!!

And an added benefit, using this API is so complex, that they will need to
keep me around to modify it. <GRIN>

On 10/20/05, Bob Cozzi <cozzi@xxxxxxxxx> wrote:
>
> Populating those "key" structures is always fun.
> First, never hard-code the length of the structure. Use something like
> %size(JEQRY) or whatever.
> Also you have a value of about 20 bytes represented in the structure, yet
> you tell it that you're passing only 12 bytes. Ain't gonna work.


You are right -- the "wonderful" documentation led me to believe that the
size parm was for the size of the key value, not the entire query
structure... Thanks!

--
"Enter any 11-digit prime number to continue..."
"In Hebrew SQL, how do you use right() and left()?..." - Random Thought
"If all you have is a hammer, all your problems begin to look like nails"