RE: Handling Record Change Journal Entries

[Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx>]

So would the data queue method you describe be using triggers or the journal receiver APIs/RCVJRNE to grab the data and stick into a data queue ?

I like the idea of processing entries from a data queue.

I think it sounds like you're not advocating triggers, right ?

Thanks.

Regards,
Richard Schoen 
Director of Document Management 
e. richard.schoen@xxxxxxxxxxxxxxx 
p. 952.486.6802 
w. helpsystems.com 
------------------------------

message: 4
date: Fri, 4 Jan 2019 11:55:55 -0600
from: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
subject: RE: Handling Record Change Journal Entries

VERY STRONG SUGGESTION:  

Assuming you want real time but not synchronous in the transaction, and you
don't want to slow down the application process, strongly consider building
a data queue system to accomplish the task.

The Trigger does nothing more than grab the data you want and enqueue an
entry on a data queue.  Could be keyed nor not, set up the way you like it.

Now build a data queue processing program that will take a queue entry and
do what you need with it.  Many of them could be running so there's no
chance it will fall very far behind if at all.

The trigger moves extremely fast, does not slow down production transactions
and while it's asynchronous it does not feel that way since the data queue
programs keep ahead of the trigger.

Last year I had too many customers implement triggers without thinking it
through all the way and we wound up with transactions that went from
microseconds to many seconds waiting on triggers.  Worse, they set up
cascading triggers and really bolixed things up.   In one case a series of
cascading triggers ended up causing themselves to fire again, and the system
wound up tight to absolute capacity, causing use to kill the partitions from
the HMC.  Bad.  

Triggers are wonderful, until they are not....... 


--
Jim Oberholtzer
Agile Technology Architects