--- Carsten Flensburg <flensburg@xxxxxxxxxx> wrote:
> - I think that the behaviour you're experiencing is a result of the
> DELAY parameter never getting into action because the specified 
> timeframe is achieved before there's any chance to wait for journal 
> entries to be added.
> I do agree that the documentation is not very specific on this point,
> but that's of course of little help to solve your problem..!
> - Another approach would be using the QjoRetrieveJournalEntries API to
> extract the journal entries you're after directly into your program.
> That way the program would be in control all the way - including when
> requested range of journal entries have been retrieved, so that you at
> that point are able to flush the outputfile buffer using the FEOD 
> opcode. Let me know if you want an RPG/IV sample of that API.
> Best regards,
> Carsten Flensburg

Thank you, again, Carsten!

Even though it doesn't directly solve the immediate problem, I have
learned more about this useful, but somewhat complicated command.

Before you even mentioned it, I thought of looking at the
QjoRetrieveJournalEntries API for the same reason, that the RPG program
controls the retrieving of the journal entries.  But I felt that I might
be reinventing a major wheel, considering that the existing application
"works" oh-so-close-just-give-me-the-da*n-records-in-the-buffer.  I'm
still of the mindset to try the OPNDBF & CLOF surrounding the RTVJRNE in
the CL that I mentioned in my last post.

But in case that doesn't pan out, I'd like to take you up on your generous
offer of the sample code.


Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.