The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact email@example.com.
I think you may be better served to have the web services jobs write their results (records) to a data queue, and have a single program that reads from that *DTAQ and writes to a file ... (that could even be "Program B" in your original post that could also act as the "listener"...)
Data queues perform much better than any database file I/O, either native or SQL-based.
Also, you could then have each web services program send a special message like "**EOF**" (or "*I AM DONE*") to tell the listener job when it has finished ... this should make it much easier for "Program B" to know for certain when they are all finished.
Just my two cents ... :-)
Mark S. Waterbury
On Monday, November 15, 2021, 04:35:24 PM EST, Jerry Forss <jforss@xxxxxxxxxxxxx> wrote:
I am adding some additional logging to nail it down.
I am having a sneaking suspicion that the web service pgms are NOT actually done. That would make the most sense.
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Charles Wilt
Sent: Monday, November 15, 2021 3:19 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: FRCRATIO issue
I second FEOD(N)..
Additionally, I'll say that FRCRATIO(1) is never the right answer now-a-days...
Lastly, if the submitted web programs are truely done, ie. those jobs have ended. Then there shouldn't be any reason not to see the records regardless of FRCRATIO() or the use of FEOD(N).
As an Amazon Associate we earn from qualifying purchases.