Peter,

This is exactly the method I use on all my triggers, except you never want
to use a CL as the originating trigger "shell" program because it, by
default, always ends like an RPG program with LR on.  Therefore, incurring
the very high overhead of recreating the CL program on every single record.
Go ahead and use an RPG program without LR as the "shell" and performance is
quite good.

I also write all errors encountered, including the "inactive" trigger
situation you mentioned, to a log file which I keep an eye on for early
indications of any problems going on.  If you leave all programs and service
programs activated, and stay away from anything that call CL's,  performance
is not an issue.

> -----Original Message-----
> From: Peter Dow [SMTP:pcdow@yahoo.com]
> Sent: Wednesday, December 05, 2001 11:16 PM
> To:   midrange-l@midrange.com
> Subject:      Re: Triggers
>
> Hi Eric,
>
> I never did see the original for this.  One software vendor I know of
> actually has a CL trigger program that calls an RPGLE program that reads a
> file keyed by file name - each record contains the name of a trigger
> program
> and a status flag as to whether that trigger program is active or not --
> and
> for each active record, calls the trigger program.  Oh, and that's not
> all.
> It also reads another file to determine whether changes triggered by a
> particular user are processed or not.
>
> I'm not advocating this method, I'm simply stating that it's in use.  And
> yes, performance was not what you'd call optimal.  For normal user updates
> via the application it could keep up.  But once one of the analysts did an
> SQL UPDATE (the user profile was not in the "ignore" file) and it took a
> couple of hours for the trigger programs to catch up.
>
> I think the data queue method mentioned by Alex Moore is a far better
> method
> of handling the requirement.
>
> Regards,
> Peter Dow
> Dow Software Services, Inc.
> 909 425-0194 voice
> 909 425-0196 fax
>


************************************************************************************************************************************************************************************************************
This message originates from Lincare Holdings Inc. It contains information 
which maybe confidential or privileged and is intended only for the individual 
or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use the 
contents of this message.
All personal messages express views solely of the sender, which are not to be 
attributed to Lincare Holdings Inc., and may not be copied or distributed 
without this disclaimer.
If you received this message in error, please notify us immediately at 
MailAdmin@lincare.com or (800) 284-2006.
************************************************************************************************************************************************************************************************************


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2022 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.