|
Al, So the bottom line of your advice is this: If you want recovery capability up to the last time someone pressed the ENTER key, use a HA solution (which costs big bucks). If you expect to depend on Journalling as a poor-man's solution, there's a good chance that you are fooling yourself. You can set up procedures so that you can be fairly confident in recovering from your last SAVLIB (or SAVwhatever), but the confidence level in applying journal changes goes down quickly. Thanks for the info, Al. It's not what I wanted to hear, but I appreciate your frankness. Phil Message: 10 From: barsa@barsaconsulting.com Subject: Re: APYJRNCHG To: midrange-l@midrange.com Date: Wed, 22 Aug 2001 13:55:32 -0400 Reply-To: midrange-l@midrange.com Clearly you could use them together. Journaling was an availability enhancement that came out in Release 4.1 of CPF. People that were interested in highly available systems went to it immediately. SAVCHGOBJ was introduced in Release 5.0 of CPF, and it was assumed that anybody that would be using it would first be using journaling. (So the default for OBJJRN was set to *NO.) SAVCHGOBJ was always very slow, because every internal object was interrogated at the object detail level to determine if it should be saved, hence you would want to be journaling as the first line of defense. Since then, two things have happened. 1). Tapes have gotten dramatically faster. 2). An internal object changed bit was added in V2R1M0 of OS/400, which made SAVCHGOBJ run much faster. Today, most people only journal because of the following needs: 1). Use of a HA product like MIMIX. 2). The desire for commitment control, which is a good thing, and not enough people program for it. 3). The use of selected rules of referential integrity. If this answers your question that's great, or else give a call. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.