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

Subject: RE: Handling Record Change Journal Entries
From: "D*B" <dieter.bender@xxxxxxxxxxxx>
Date: Sat, 5 Jan 2019 08:30:18 +0100
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>

... if you are needing transaction safety (and you should!!!), RCVJRNE would be the easiest way. Needing synchronous replication, triggers would be the easiest way.
Using the dataq approach with multiple DataQ listeners, you would loose transaction safety. Replicating to a remote system (as400 or not), best would be to let the apply process run remote.

D*B

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Handling Record Change Journal Entries , Jim Oberholtzer

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