|
John, May be the programmer arguing against CC is a good programmer (and I'm not sure about), but certainly he does not understand the OLTP environment. You already decided to use journals and I advise to use the "BOTH" option (2 images). CC is the best and fast way to ensure transaction integrity. The other way to do so causes a much graeter overhead, but some consevative programmers cuntinue to use it. It was used during the early release of CPF (S/38 OS). The 2 images journal helps you not only to achieve a better restore in case of disk crash but also to go back (remove changes) in case a bug is caused data damages und you must clean your files and reinsert the changes. the 2 major points against journaling and CC are a, the performance overhead and b, the disk space used by the receivers. My experience (we use journals since S/38) shows the overhead is very minor, and now the hardware is very cheap, and the receivers can be detached, saved and deleted some times during the day and is very easy to write automatic/scheduled procedures. My opinion is based on my experience as the DP manager of an AS/400 site serving about 1,200 interactive users in about 170 remote brances. Joseph Wechsler John Hall wrote: > > We are in the midst of doing some conversions to old software. One of > the programmer/consultants we brought in is arguing against setting up > commitment control. I feel that it is a feature we should be using. > > He feels that there may be too much overhead on the system. We are > going to enable journaling on all these files anyway. > > We are on a Model 170 2164. We just moved from an F10 so we can afford > some overhead in processing time. > > What is the general feeling on this ? If we are posting a batch of 500 > records should we commit on every record, every 10th record or after the > entire batch ? > > I think it may be a case of lack of knowlege on his part but I would > like some other opinions. > > John L. Hall > Home Sales Co. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.