Nope, the RPG program buffer (aka blocking) is specific to the program/file
So even if you have the same physical file defined with two different
f-specs (one OUTPUT one INPUT) the program can't see data in the OUTPUT
buffer when reading via INPUT.
Perhaps you're thinking of the "buffering" done by the DB itself. A write
to the DB stays in memory, it doesn't (usually) go straight to the disk.
That data can be seen by other programs.
Make sure to use FEOD(N)...that flushes the RPG program buffer to the DB
without forcing the DB to flush to disk. Much better performance than the
straight FEOD which flushes all the way to disk.
On Tue, Apr 15, 2014 at 12:53 PM, Darryl Freinkel <
I have commitment control turned off and am using commit(*none).
I see the writes are not written in SQL so I will add the FOED and check
I thought records in the buffer were supposed to be able to be read by the
programs in the job?
Sent from my Android device with K-9 Mail. Please excuse my brevity.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives