Re: Does trying to add a trigger lock the file?

[William Washington III <w.washington3@xxxxxxxxxxxxx>]

Rob,

Excellent idea.  99% of the triggers I write takes the record I'm interested in
and immediately writes it to a data queue.  I want my triggers to do as little
work as quickly as possible.  Typically, my "generic" trigger services several
files at once, but sends the record to the appropriate queue for processing.

Async programs service the data queue, doing all of the other processing I need
without putting a "drag" on the primary application.  If high volume is
occurring, I can just start up another data queue service program temporarily
to handle the higher transaction rate.  We don't want our arrival rate greater
than our service rate!

My only problem here is one of the files is soooo busy, I can't get a lock on
it for the 2 seconds it will take to apply the trigger.

William

> date: Thu, 2 Dec 2004 09:06:23 -0500
> from: rob@xxxxxxxxx
> subject: Re: Does trying to add a trigger lock the file?
> 
> One suggestion, if it is that much of a bear to get a lock, add an 
> extremely basic program as a trigger, and have it call your other 
> programs.  That way the lock won't be a problem when you have to 
> add/modify programs.  And, until you get this working, I'd leave your 
> *inlr on upon exit until you get it thoroughly stress tested.  That way 
> the current version of the program gets loaded.
> 
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com


=====
=============================
William Washington III
Njia Systems Incorporated
w.washington3@xxxxxxxxxxxxxxx
312-719-0519
=============================