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

[Adam Glauser <adamglauser@xxxxxxxxxxxx>]

I wrote:
>> 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.
> > What I'm looking for is recommendations on whether or not FRCRATIO, 
> > FEOD, or neither are the way to go in this situation.

Scott Klement wrote:
> 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).
>
> BLOCK(*NO) is extremely easy to code.  You might just try it and see if 
> it performs respectably.

I ended up going this route, and it is to be working well.  It certainly 
helped tracking down the problem.

Thanks again to everyone who responded.  I've learned a lot from this 
discussion.