|
Hello GA, - 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 the 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 ----- Original Message ----- From: "G Armour" <garmour400m@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Wednesday, March 17, 2004 4:21 PM Subject: Re: RCVJRNE exit program never getting '0' (no more entries) in 2ndparameter > > ANYWAY, the problem of the output file remaining open in the exit program > and the buffer hiding records waiting to be flushed still remains. The > job has steps following the RCVJRNE that require the records still sitting > in the buffer. > > I'm going to try using OPNDBF before the RCVJRNE, and then CLOF > afterwards, to see if this will force the file to close. > > Also, I wonder if it would have been more appropriate to use DSPJRN to an > outfile in this application. (There may have been concerns about the size > of the outfile on a space-starved system.) ########################################### This message has been scanned by F-Secure Anti-Virus for Internet Mail. For more information, connect to http://www.F-Secure.com/
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.