RE: Handling Record Change Journal Entries -- MIDRANGE-L

Subject: RE: Handling Record Change Journal Entries
From: Rob Berendt <rob@xxxxxxxxx>
Date: Fri, 4 Jan 2019 13:28:13 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I would NOT interpret any of Jim's comments as saying he is not advocating
triggers. Instead I would interpret them as saying this:

Instead of this:
RPGTRIGPGM
Get trigger parms
process the parms and do nifty stuff like notify inventory shortages,
duplicate data to OLAP remote site, email thank you letters, etc

You would do this:
RPGTRIGPGM
Get trigger parms
Write parms to data queue

RPGDTAQPGM
Read data queue
process the data queue entry and do all the nifty stuff

This way if the data queue program takes awhile to do it's task, or it
just blows up, your online systems are not affected.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Handling Record Change Journal Entries , Jim Oberholtzer
RE: Handling Record Change Journal Entries , Musselman, Paul

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