Mmm. Unless you are specifying a REFFDATE every time you run your SAVCHGOBJ(
eg., REFDATE(&yesterday) ), the command does default to the last
SAVLIBdate. As per the V5R4
Reference date (REFDATE)
Specifies the reference date. Objects that have been changed since this
date are saved.
**SAVLIB*The objects that have been changed since the date of the last
running of the Save Library (SAVLIB) command are saved. If the specified
library was never saved, a message is issued and the library is not saved,
but the operation continues. *date*Specify the reference date; objects that
have been changed since this date are saved. If you specify a date later
than the date of the running of this command, a message is issued and the
operation ends. The date must be specified in the job date format.
----------------------So, by default, the system does save the objects
using the last SAVLIB date as a starting point, regardless of the change
I have always used UPDHST(*NO) when I do things like temporal ("just in
case") backups. (for example, when I am about to modify a zillion records).
That way, I don't change the object's info. Again, using the infocenter as
Update history (UPDHST)
Specifies whether the save history information of each saved object is
changed with the date, time, and location of this save operation. The save
history information for an object is displayed using the Display Object
Description (DSPOBJD) command. The save history information is used to
determine which journal entries are processed when RCVRNG(*LASTSAVE) and
FROMENT(*LASTSAVE) or FROMENTLRG(*LASTSAVE) are used on the Apply
**YES*The last save date, time, and location is updated in each object
saved. **NO*The save history information contained in the description of
each object saved is not updated.
*Note: *UPDHST(*NO) should be used for a save operation that is not
intended for recovery. For example, if the save data is sent, record by
record, to another system and the save file immediately deleted, the save
history information is probably not to be updated.
IBM Certified Systems Expert — eServer i5 iSeries