Re: File Trigger Performance

[Charles Wilt <charles.wilt@xxxxxxxxx>]

 READ Triggers generally have a much worse affect on performance than
INSERT/UPDATE ones...
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/dbp/rbaforzahftre.htm

"use read triggers with extreme caution. Using a read trigger causes a
trigger to be called for every record that is read and may be called for
records that are positioned to but not read. During a query, this means
that triggers can be called many times as records are processed multiple
times by the query. This can effect system performance."

The CLLE is possibly a problem...

I don't believe there's anything static in a CLLE module...so for every
record, you're executing RTVJOBA or calling the QUSRJOBI API right?

I'd look at calling  QUSRJOBI API from an RPG module with static variables,
so that it only need to be called once in the job.

Charles



On Mon, Apr 9, 2018 at 9:50 AM, Rich Loeber <rich@xxxxxxxxx> wrote:

>    I have a customer using one of our products that employs a physical file
>    trigger program for READ.  The trigger program is an ILE program that
>    starts up in a CLLE.  The first steps in the CLLE are to retrieve the
> run
>    status (batch or interactive) and then check a setting in a data area.
> If
>    the job is running in batch and the setting from the data area tells the
>    program to ignore batch reads, then a RETURN is immediately issued.
>
>    Seems easy enough, but the customer is reported very poor performance
> now
>    on batch applications.
>
>    Any ideas?
>
>    Rich Loeber - @richloeber
>    Kisco Information Systems
>    [1]http://www.kisco.com
>
>    ------------------------------------------------------------
> --------------
>
> References
>
>    Visible links
>    1. http://www.kisco.com/
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://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