|
I used to run a MACPAC shop (an ERP package like BPCS or JDE). It used full journaling and commitment control. I have been trying to spread the word about the benefits of journaling ever since. Based on that experience, I would recommend: - one journal per data library (i.e. - journal dozens or hundreds of files to the same journal) - journal all your 'important' files - store the receivers in another library in a separate ASP. This way, if the data is in ASP1 and the receivers are in ASP2, losing ASP1 is less painful - restore ASP1 from tape and roll forward using the receivers in ASP2 - journaling only the after image is good for rolling forward after a failure. Journaling BOTH allows you to roll back failed transactions or batch jobs. - consider using commitment control. It's a pain in the neck to implement, but when it's done properly, you can really sleep better at night. Journaling is helpful, but commitment control is wonderful. I feel so strongly about the topic of journaling and commitment control, I will be making an hour presentation at three upcoming meetings - the New England IBM User Group Conference (www.neibmconf.com) on 3/28 and 3/29, the UK IBM Computer Users Association (www.compusol.co.uk - sort of a UK Common) on 4/3 thru 4/5, and at Common in Bremen, Germany (www.comeur.org) on 5/15/ thru 5/18. While I'm really going to these meetings to be a vendor hawking my wares at a booth, this is one topic that I feel very strongly about. If you're running a big, expensive software package and the vendor didn't build in journaling and commitment control, they should have... +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Purge and Archive your AS/400 Data Without Programming with ARCTOOLS (tm) DCSoftware, Inc. (508) 435-8243 (508) 435-4498 (fax) http://www.arctools.com mailto:info@arctools.com +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ----- Original Message ----- From: "Mark Allen" <markallen@kellyskids.com> To: "'MIDRANGE-L" <MIDRANGE-L@midrange.com> Sent: Tuesday, March 21, 2000 10:52 AM Subject: Journaling question..... > We are getting ready to embark on a project where we will be journaling our > major files, mostly for auditing/control checking (i.e. nobody admits to > changing customer order, changed by someone who should not have capability, > etc). Interested in approach others have used. One journal per > physical???, all PF's in one journal, one journal per app/module, etc???? > > Mark Allen > IS Manager > Kelly's Kids > markallen@kellyskids.com +--- | 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.