× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yeah that's how I would do it manually, I'm thinking more of the right click set as publisher, right click select as subscriber wizard type of stuff like you do in MS SQL.

I'm wondering where that exists in DB2, perhaps it's in iSeries navigator somewhere.

I'm also looking for all the replication topology options. Documentation is nowhere to be found.

-----Original Message-----
From: Chris Bipes [mailto:chris.bipes@xxxxxxxxxxxxxxx]
Sent: Monday, March 11, 2013 2:54 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Bi-directional transactional replication on IBM i

We have a few files that we replicate across 3 systems. All three update the files. We basically wrote a module to perform all the files updates. We use before and after images from a trigger to do field level updates. We chain to the record w/lock and compare the before to after at the field level, if the field changed, compare the before to the current, if the same we update. If Programming logic appears to be complex but it is one set of code repeated for each field. Makes heavy use of externally described data structures, b.field = before, a.field = after, and plain field = current. You can log any conflicts and update the field with the new value anyway discard the update to the field. Which ever you choose. It does require you to send both the before and after images to the remote system(s). For the most part, we do not see the same record being update on multiple system before the previous updates have been applied. We also use data queues to store and upda tes until the remote system can read the data queue.

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Matt Olson
Sent: Monday, March 11, 2013 12:25 PM
To: Midrange Systems Technical Discussion
Subject: RE: Bi-directional transactional replication on IBM i

Only database.

-----Original Message-----
From: Chris Bipes [mailto:chris.bipes@xxxxxxxxxxxxxxx]
Sent: Monday, March 11, 2013 2:11 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: Bi-directional transactional replication on IBM i

Bi-direction replication is very tricky. Are you talking just about database changes or object level changes including the IFS?

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.