Re: Equivalent to FEOD in SQL

FEOD exists because the RPG language will buffer output data.

In other words, a WRITE in RPG doesn't necessarily send the data to the DB.
FEOD(N) tells RPG to flush it's buffer to the Db.
FEOD also flushes the buffer to the Db and forces the Db to write to
secondary storage.

I've never heard nor seen any type of similar buffer used by SQL. An
INSERT/UPDATE via SQL is direct to the DB.

The only reason I've seen for writes via SQL to not show in another job is
when they are done under commitment control and another job is running
under an isolation level doesn't doesn't allow it to see the
uncommitted data.

I don't know what may be going on, but I'm pretty sure it's not what you
think.

Charles

On Tue, Oct 6, 2020 at 7:45 AM Paul Bailey <PabloMotte+Midrange@xxxxxxxxx>
wrote:

We require the FEOD op code at times to force the RPG data writes to finish
before we call an additional routine to process that data.

When using embedded SQL I am having to write a few seconds pause in RPG
before calling the next routine to ensure the data has been written because
FEOD does not appear to work on SQL written data, but this is not ideal and
seems like a poor workaround.

Is there an equivalent to FEOD when the data has been written by embedded
SQL statements in an SQLRPGLE program?


TIA

-Paul/
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com