RE: Replication Opinions

["Morgan, Paul" <Paul.Morgan@xxxxxxxxxxx>]

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.