RE: SAVCHGOBJ question - rephrased

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

Y'all

I've just started to do something like this. I found that SAVCHGOBJ will
keep saving the same things unless you have a SAVLIB in between. New
objects have no SAVLIB date in them-or something like that. Someone
mentioned doing daily SAVCHGOBJ and weekly SAVLIB.

I've gone around this with a DTAARA with the date & time of the last daily
save operation. Then I use that on SAVCHGOBJ in the REFDATE/REFTIME parms.

Same can be done on SAVDLO (REFCHGDATE/REFCHGTIME parms) and on SAV, for
IFS (SAVPERIOD parm, first 2 elements).

These commands must all have been written by different groups - output
options are different, these last changed parms are different - that''s why
we need ROBOT/SAVE or BRMS, eg?

Regards

Vern

At 10:40 AM 9/16/02 -0500, you wrote:
> Dennis -
>
> The reason (IMHO) that your SAVCHGOBJ runs the same amount of time with your
> large libs omitted is that you said earlier that you also save these
> libraries to a SAVF and then back up the SAVF.  Since the SAVCHGOBJ uses
> REFDATE(*SAVLIB) if you had just saved these libraries to a save file there
> would be no changed objects in them.  If you monitor performance data you
> may want to consider omitting your Performance Data Library (usually
> QPFRDATA).
>
> It is true that there is no IBM command that does a restore of changed
> objects for *ALLUSR, you need to know all of the libraries on the tape that
> you are restoring changes from.  There is a TAATOOL command, RSTALLCHG that
> I believe will also do this.
>
> Scott Ingvaldson
> System Administrator
> GuideOne Insurance Group