Re: Buffering of DB output with *INLR=*OFF

Scott Klement wrote:

Adam Glauser wrote:

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 definitely wouldn't use FRCRATIO. Instead, I'd do one of two things:

a) Code BLOCK(*NO) on the F-spec.

b) Run the trigger in a named activation group. Then reclaim the activation group when the user returns to the menu (or some other opportune time).

Thanks for the suggestions. I haven't used BLOCK(*NO) before, but I'll explore that. Explicitly reclaiming the activation group is also a good thought (which I should have come up with myself). This is an application that people spend all day in, so unfortunately it's not quite as simple as putting the RCLACTGRP in the menu program.

Or, if you absolutely must use FEOD (though I can't see why you'd do that in a trigger where you're dealing with one record at a time) then you'd be better with FEOD(N), instead of a straight FEOD.

I didn't really think FEOD was the way to go, but I thought I'd confirm.

The disadvantage to (b) is that running in a named activation group can get confusing with commitment control, since your trigger wouldn't necessarily be within the same commit definition as the program doing the actual updates. So writes to your log file wouldn't get rolled back a the same time as writes to the actual file, which can be sloppy.

Commitment control is not involved in this case. It is good to know about this consideration for future reference.