× 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 support@midrange.com.



Whatever you do, don't use FRCRATIO if performance is important.

Don't use FEOD either.....

However, if you're on a recent OS version, FEOD(N) could be used.

FEOD(N) flushes the RPG buffer to the DB, so you can see the records, but doesn't force the data to
disk. So the performance hit of FEOD(N) isn't as bad as that of FEOD without the (N).

Note if you're writing your log for every record, then journaling is probably the better solution. On
the other hand, if you only write the log record when there is a problem, a trigger is a good
solution.


HTH,

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Adam Glauser
Sent: Tuesday, April 08, 2008 3:29 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Buffering of DB output with *INLR=*OFF

I think this is a mixed RPG / i5/OS question, but I'm not entirely sure.
Please send me to Midrange-L if I'm off topic.

One of our primary applications is misbehaving. Some fields on one of
the main files are getting updated incorrectly, but I am unable to
duplicate the problem. I have been able to determine that the problem
records have *loval in a particular date field.

My solution is to write (my first) trigger program which will log the
name of the entity updated and the program making the change. I don't
have exact statistics, but I believe that many updates to this field
occur during the course of normal operations. Since my *AFTER *UPDATE
trigger will be firing many times, I want it to be fast, so I'm leaving
my log file open and exiting with *INLR=*OFF.

I've noticed in my testing that the records I write to the log file in
the testing job don't show up until the testing job ends. I'm using DBU
to look at the file, in case that matters. I know that writes are
buffered and that I can use FRCRATIO or FEOD, but I don't really want to
override the buffered writing unless it's absolutely necessary.

What I'm looking for is recommendations on whether or not FRCRATIO,
FEOD, or neither are the way to go in this situation. I don't know
enough about write buffering to know whether it could cause performance
problems in the given situation, say when a lot of people end their
interactive jobs at shift change time.

I hope that most of that was relevant, and please let me know if I'm
completely misunderstanding this.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.




This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.