RE: Triggers

We use triggers extensively.  If you follow a few simple guidelines, there
is no noticeable performance "hit".  The most basic and important rule is -
ONLY PERFORM ESSENTIAL LOGIC WITHIN THE TRIGGER PROGRAM.  When possible,
perform NO logic - just pass the buffers on to a separate process.  If the
trigger program calls other programs, or opens and closes a bunch of
database files, or performs the unpardonable sin of causing another trigger
to fire, you will NOT be happy.

Alex  ( Don't ask how I know )

> -----Original Message-----
> At 13:20 12/06/2001, Peter Dow wrote:
> >what those programs do, etc.  It would be interesting to
> know just how much
> >of a performance hit that initial CL is adding though...
>
> All I can offer is some anecdotal evidence. I tried using CL
> for format
> selector programs once. A format selector is like a trigger
> that doesn't do
> anything but receive the buffer, set an internal code value
> and exit. I was
> horrified to find that in addition to initializing and
> freeing automatic
> storage for every record, it was writing a message to the
> joblog that said
> it was terminating because it had reached the end of its
> code. I don't have
> any timings, but the overhead was prohibitive, and moving to
> RPG fixed the
> problem.
>
>
> Pete Hall
>