Re: Records written not seen by called program

[Jon Paris <jon.paris@xxxxxxxxxxxxxx>]

Just to add a point of clarification.

FEOD(N) and FEOD do different things.

The (N) extender causes the buffer to be released back to the OS and is a very fast function. Without the extender an FEOD will cause the buffer to be physically written back to disk and is much slower.

I _think_ (and hopefully Barbara can clarify) that FRCRATIO(1) has the same impact as using FEOD with no extender except that it will impact to each and every operation. The benefit of using FEOD is that you can get the performance benefit of allowing blocking to take place but still ensure that records are written away before they are needed by another program. FEOD(N) is an even more efficient way to achieve that at the slight risk that if the system dies the data may not end up back on disk. Not sure where Block(*No) would fit into the picture. I suspect that it is at the same level as FEOD(N) but again with the restriction that it applies on each and every operation.
 
 
Jon Paris

www.partner400.com
www.SystemiDeveloper.com

> On Dec 6, 2016, at 2:55 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
>
> having a unique key disables the buffering RPG does, since the DB has to
> know about the record to enforce uniqueness; which has performance
> implications.
>
> FRCRATIO(1) disables the RPG buffering along with the DB "buffering"
> inherit to single level store by forcing a write all the way to disk; which
> of course has even bigger performance implications.
>
> The "best" way to solve the issue is to use FEOD(N).
>
> Charles
>
> On Tue, Dec 6, 2016 at 12:38 PM, Roger Harman <roger.harman@xxxxxxxxxxx>
> wrote:
>
> > Thanks.  I considered FEOD, but may not be able to modify the caller so
> > quickly.
> >
> >
> > Still hoping to confirm the dirty record issue vs unique key.
> >
> >
> > Roger Harman
> >
> > COMMON Certified Application Developer - ILE RPG on IBM i on Power
> >
> >
> >
> >
> >
> >
> >
> > ________________________________
> > From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Charles
> > Wilt <charles.wilt@xxxxxxxxx>
> > Sent: Tuesday, December 6, 2016 11:30 AM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: Records written not seen by called program
> >
> > FRCRATIO(1)  is a bad old idea...
> >
> > Add a FEOD(N) before calling PGMB.  That will flush RPG's buffer....
> >
> > Charles
> >
> >
> > On Tue, Dec 6, 2016 at 12:07 PM, Roger Harman <roger.harman@xxxxxxxxxxx>
> > wrote:
> >
> > > I have a process that has failed a couple of times.  PgmA writes a record
> > > and then calls PgmB with they key info.  On rare occasions, the chain to
> > > the file from PgmB fails.
> > >
> > > The file in question is not unique keyed and I'm wondering if the record
> > > is being buffered and not visible to the called program.  I recall
> > reading
> > > something about that a long time ago and that the fix is to have a unique
> > > key (LF?) over the physical file.  Is that correct?  Is FRCRATIO(1)
> > > essentially the same thing?  It's not a high volume process.  Maybe
> > 12,000
> > > records on a busy day.
> > >
> > > Thoughts?
> > >
> > > Thank you.
> > >
> > > Roger Harman
> > > COMMON Certified Application Developer - ILE RPG on IBM i on Power
> > >
> > >
> > >
> > >
> > > --
> > > 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,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > [http://lists.midrange.com/images/small-family.gif]<http:
> > //lists.midrange.com/mailman/listinfo/midrange-l>
> >
> > MIDRANGE-L Info Page<http://lists.midrange.com/mailman/listinfo/midrange-l
> > >
> > lists.midrange.com
> > To unsubscribe from MIDRANGE-L, get a password reminder, or change your
> > subscription options enter your subscription email address:
> >
> >
> >
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > midrange.com -- MIDRANGE-L mailing list archive<http://archive.
> > midrange.com/midrange-l>
> > archive.midrange.com
> > midrange.com MIDRANGE-L mailing list archive
> >
> >
> >
> > > Please contact support@xxxxxxxxxxxx for any subscription related
> > > questions.
> > >
> > > Help support midrange.com by shopping at amazon.com with our affiliate
> > > link: http://amzn.to/2dEadiD
> > [http://g-ec2.images-amazon.com/images/G/01/social/api-
> > share/amazon_logo_500500._V323939215_.png]<http://amzn.to/2dEadiD>
> >
> > Amazon.com: Online Shopping for Electronics, Apparel, Computers, Books,
> > DVDs & more<http://amzn.to/2dEadiD>
> > amzn.to
> > Online shopping from the earth's biggest selection of books, magazines,
> > music, DVDs, videos, electronics, computers, software, apparel &
> > accessories, shoes, jewelry, tools & hardware, housewares, furniture,
> > sporting goods, beauty & personal care, broadband & dsl, gourmet food &
> > just about anything else.
> >
> >
> >
> > >
> > --
> > 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,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > [http://lists.midrange.com/images/small-family.gif]<http:
> > //lists.midrange.com/mailman/listinfo/midrange-l>
> >
> > MIDRANGE-L Info Page<http://lists.midrange.com/mailman/listinfo/midrange-l
> > >
> > lists.midrange.com
> > To unsubscribe from MIDRANGE-L, get a password reminder, or change your
> > subscription options enter your subscription email address:
> >
> >
> >
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> > midrange.com -- MIDRANGE-L mailing list archive<http://archive.
> > midrange.com/midrange-l>
> > archive.midrange.com
> > midrange.com MIDRANGE-L mailing list archive
> >
> >
> >
> >
> > Please contact support@xxxxxxxxxxxx for any subscription related
> > questions.
> >
> > Help support midrange.com by shopping at amazon.com with our affiliate
> > link: http://amzn.to/2dEadiD
> > [http://g-ec2.images-amazon.com/images/G/01/social/api-
> > share/amazon_logo_500500._V323939215_.png]<http://amzn.to/2dEadiD>
> >
> > Amazon.com: Online Shopping for Electronics, Apparel, Computers, Books,
> > DVDs & more<http://amzn.to/2dEadiD>
> > amzn.to
> > Online shopping from the earth's biggest selection of books, magazines,
> > music, DVDs, videos, electronics, computers, software, apparel &
> > accessories, shoes, jewelry, tools & hardware, housewares, furniture,
> > sporting goods, beauty & personal care, broadband & dsl, gourmet food &
> > just about anything else.
> >
> >
> >
> > --
> > 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,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxx for any subscription related
> > questions.
> >
> > Help support midrange.com by shopping at amazon.com with our affiliate
> > link: http://amzn.to/2dEadiD
> -- 
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD