RE: SAVF definition

["Andy Nolen-Parkhouse" <aparkhouse@xxxxxxxxxxx>]

Rob,

The save files are backups created using standard OS/400 save commands.
Instead of specifying a tape drive, the command refers to the save file.  If
these objects truly have not been touched in five years, I would suggest
that you follow the steps below:

DSPSAVF - This will give you a printout, similar to a DSPTAP with the
*SAVRST option.  Print out a few copies for each save file and put them in a
safe place.

SAVSAVFDTA - This will put the save file data onto tape in a way that allows
objects to be restored directly from tape.  Alternatively you could just
save the save files as objects (remember to specify SAVFDTA(*YES)), but you
would need to restore the save file and then restore the objects from the
save file.  Make at least two tapes.

Delete the save files. - Once you have listings of the contents and multiple
backups, you can delete them from the system.  Chances are very good,
(assuming that this is a vendor package), that these save files were created
as part of an upgrade.

I grew up in Southern California and remember the fires.  Unless you have an
emergency of your own, it strikes me as reasonable to wait until your
colleague is less preoccupied.

Regards,
Andy Nolen-Parkhouse



> HI all.
> 
> Can anyone please give me a definition (using words of one syllable or
> less)
> of a Save File?
> 
> I have been giving the task of cleaning up our production machine and
> there
> are SAVF objects created and last used late 1997 (yeah 1997!!) but the
> user
> doesn't want them removed because they "may still be used by the module".
> (It's Friday, in California where a wild fire is burning homes close to
> the
> user's home - so I suppose I should give her the benefit of the doubt.)
> 
> TIA.
> 
> 
> Rob Joubert