Re: Handling Record Change Journal Entries

You are correct except the best way to ensure transaction safety is with commit control, triggers or not. Triggers in and of themselves do not ensure transaction integrity, they complicate it.

The original post I believe was to siphon off data for other purposes in as real time as could be expedient without affecting the transaction performance.

Jim Oberholtzer
Agile Technology Architects

On Jan 5, 2019, at 1:30 AM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

... 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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com