• Subject: Re: Triggers (and I don't me Roy Rogers' Horses)
  • From: DAsmussen@xxxxxxx
  • Date: Wed, 26 May 1999 21:58:44 EDT


In a message dated 5/26/99 1:10:39 AM Eastern Daylight Time, 
PaulMmn@ix.netcom.com writes:

> Well, we're finally going to use some triggers on our system.
>  We're concerned about the overhead of running the little monsters
>       - Where does the overhead show up?  The job that kicks off the
>  Trigger?  The subsystem?  The OS (as part of QDBSRV?)?
>       - Is there a convenient place to monitor for the additional load?
>  If anyone can provide a 25-words-or-less answer, or point me at the Right
>  Fine Manual, I'd be greatly gratified.

I've been using, and abused by, triggers almost since their inception.  
Written correctly, the overhead is practically nonexistant.  I don't know of 
any way to track trigger overhead explicitly.  Keep them small, avoid calls 
to other programs from the trigger if at all possible, and eliminate job log 
generated messages like "Open of file nnnnnnnnnn was changed to 
SEQONLY(*YES)" because they slow things down and will bomb any job that 
activates the trigger that is not set to *WRAP or *PRTWRAP if it activates 
the trigger too many times.  Sorry to exceed 25 words, but then, so did you!


Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-mail:  DAsmussen@aol.com

"It's impossible to make anything foolproof, because fools are so ingenious." 
-- Anonymous
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Return to Archive home page | Return to MIDRANGE.COM home page