Re: APYJRNCHG -- MIDRANGE-L

Hey, Al.

My only problem with this response is that it's a blanket statement implying
that journalling is of no use, and I know you don't truely believe that, do
you?

so... as I see it, what you really said was:

One of the reasons for doing Journals and SAVCHGOBJ is to recover to a point
in time.

If that point in time that you wish to recover to happens to be the point in
time where you took the save changed objects, then fine. Journals will
complicate that recovery.

Your point of ignoring journals is well founded. Most people don't take the
time to figure out a comprehensive save strategy that includes the journal
receivers being taken off the system and physically away from the site on a
regular, recurring basis other than at the same time they take the save
changed objects.

So, if the point in time is to a specific hour of the day, you need to
consider using journals and journal receivers, but, and this is a big but...
you must also consider more frequent isolation of the receivers.

This, like very fast tape drives, costs money. A complicated restore process
must be offset by the financial need to recover to more specific points in
time.

Again, if that point in time is not a factor in a site loss situation, then
not saving the journals will shave your restore time, but the journals can
allow you to recover more quickly and more precisely from say a program
induced error. (A more likely, and more frequent problem). Offsite journal
receivers can be a hinderance here.

There are always a lot of things to consider in save restore.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - AS/400 Administrator
 -- IBM Certified Specialist - RPG IV Developer

"America is the land that fought for freedom and then
  began passing laws to get rid of it."

     - Alfred E. Neuman

-----Original Message-----
From: barsa@barsaconsulting.com <barsa@barsaconsulting.com>
To: midrange-l@midrange.com <midrange-l@midrange.com>
Date: Tuesday, August 21, 2001 10:07 PM
Subject: Re: APYJRNCHG


>
>Forget using your journal entries as a part of the restore.  On SAVCHGOBJ,
>change the OBJJRN parameter from *NO (the default) to *YES.  SAVCHGOBJ was
>created when journaling was a key part of OS/400's (then CPF's) save
>restore strategy.
>
>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
>
>
>
>
>
>
>                    Jim.Nelson@RCIS-NET
>                    .COM                      To:
midrange-l@midrange.com
>                    Sent by:                  cc:
>                    midrange-l-admin@mi       Subject:     APYJRNCHG
>                    drange.com
>
>
>                    08/21/01 05:31 PM
>                    Please respond to
>                    midrange-l
>
>
>
>
>
>
>
>We are looking at shortening our backup downtime by going with SAVCHGOBJ.
>Only problem is that we journal most of our files, which means we would
>need
>to restore from the SAVEALL, then run APYJRNCHG for the daily saves.  The
>documentation says to expect a longer recovery time, but no estimates.
>
>During our 'busy time', we create about 300,000 journal entries per day -
>tables ranging from 150 bytes to over 800.
>
>1.  Anybody have estimates (or an algorithm) on what the recovery time
>would
>be?  Looking more for those occasional 'restore to a temporary library to
>check data' rather than a complete recovery.  If we ever need a reload, a
>few hours here or there will be the least of my worries!
>
>2.  Any 'tricks' or items to watch for using SAVCHGOBJ and APYJRNCHG?
>Horror stories?
>
>Thanks for your help.
>
>JN
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>
>
>
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>