Re: Triggers Vs. Journalling

If you are pushing data in one direction journaling would be the way to go.  
It's tried, true, and well tested on the iSeries.   The performance of 
journaling is better known than triggers for what you are trying to do.

It is also pretty easy to maintain once you have it up and working in terms of 
files that you need to journal or not.

<hth>

Regards,

Mike Shaw


> I'd appreciate opinions (especially if they're based on fact <smile>)
> regarding remote database synchronization. I have a situation where I
> need to keep some files updated on a remote iSeries system in the
> unlikely event the main iSeries crashes. I can't go the package route
> now due to cost constraints. Since there are only three files (but large
> ones with a lot of records), I was thinking I could trigger the files on
> the main system and write add/change/delete records to a file. I could
> then transfer the file to the remote system (every x minutes) and apply
> those changes to the corresponding remote file. I could do the same
> thing with journalling. 
> 
> Thoughts?
> 
> 
> -- 
>   
>   michaelr_41@xxxxxxxxxxxxxx
> 
> --
> 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.
>