× 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.


  1.  Home
  2. MIDRANGE-L
  3. January 2011

Re: Replication Opinions

Great replies folks...thanks very much. I need to replicate the
changes on a near real-time basis, so a once a day file transfer won't
work for me. I've written code in the past to handle updates with the
remote journaling, so I may resurrect that code and modify it to fit
the current needs. MQ is licensed to one of the systems but not the
other, so that's probably not going to help. The budget is probably
just person hours - no room for package software.

What are folks thoughts about the continuing use of DDM? I just seem
to shy away from it anymore. I know it's still viable in a TCP/IP
environment, but I find it's not my first thought when it comes to
remote file access. I'd rather have some SQL code embedded in my
program that processes a remote connect and accesses the data that
way. Of course, that's not a good option when needing to access both
remote data and local data.

Thanks...

- Michael

On Thu, Jan 6, 2011 at 4:53 PM, Morgan, Paul <Paul.Morgan@xxxxxxxxxxx> wrote:
Exactly.  If the file is small and updates aren't that frequent why go through the rigmarole of journaling, triggers or data queues.  Just blow the file over to the remote system occasionally.  *UPDADD works if someone is in the file instead of *REPLACE which requires a lock on the file.  Course the file would also have to have keys and no record locks on the remote system.  That's why it would work 'in some conditions'.

Paul

Principal Programmer Analyst
IT Supply Chain/Replenishment


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Thursday, January 06, 2011 4:09 PM
To: Midrange Systems Technical Discussion
Subject: Re: Replication Opinions

That solution would be equivalent to replacing the destination file every time.

*UPDADD doesn't "update" changed records only...it updates any
existing record in the destination from the source.

*RPLADD would have been a better name :)

Charles

On Thu, Jan 6, 2011 at 3:46 PM, Morgan, Paul <Paul.Morgan@xxxxxxxxxxx> wrote:
Michael,

There is a software package called Mimix that does that automatically but it could be overkill for just one file.

Maybe a repeated CPYF with *UPDADD run on the remote system from a DDM file would work in some conditions.

Paul

Principal Programmer Analyst
IT Supply Chain/Replenishment


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Thursday, January 06, 2011 2:55 PM
To: Midrange Systems Technical Discussion
Subject: Replication Opinions

Have a file that I need to replicate in near real time to another
system. What techniques do folks use? I'm thinking of triggers on the
from file, remote SQL connect, ACD as appropriate. I guess journaling
would be an option too. Opinions welcome. Thanks...
--
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.


--
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.


--
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.


--
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 ...
Follow-Ups:
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.