RE: SAVCHGOBJ (was APYJRNCHG)

We had an issue with SAVCHGOBJ concerning multi-member files a few years
back.  We worked with a package that relied heavily on file members as data
entry batches and as work members within job streams.

The save command saves members as they are created or changed, but it did
not account for the deletion of members.  When I performed a test restore of
a weekend save and incremental restores of daily SAVCHGOBJ changes I found
that it accumulated all file members created during the week, even though
many of the members should have been gone.  Within the context of this
software package the presence of these members would allow data to be
reposted.

I was never able to figure out if I was doing something wrong, or, even if I
was doing it right, if there was any reasonable way to produce an accurate
recovery process.

-Jim

James Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@dollargeneral.com>


-----Original Message-----
From: MCPARTLAND, Stan [mailto:stanley.mcpartland@bently.com]
Sent: Wednesday, August 22, 2001 10:56 AM
To: 'midrange-l@midrange.com'
Subject: SAVCHGOBJ (was APYJRNCHG)


<snip>

I can not currently think of a reason that someone should be uncomfortable
with the SAVCHGOBJ command.

<snip>

One caution about SAVCHGOBJ.  If you run a SAVLIB that is not part of your
normal backups and specify or default to UPDHST(*YES), you may have a
problem.  SAVCHGOBJ may skip objects that you want saved since you updated
the last saved date for the library.  There are at least two ways to prevent
this situation.  1) Use a REFDATE and REFTIME controlled by your backup
routines and not the default *SAVLIB, or 2) make sure to specify UPDHST(*NO)
when you use SAVLIB to save objects outside of your normal rotational
backups.

Regards,
Stan
_______________________________________________
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