Re: savrstobj questions

On 02 Aug 2012 12:40, fbocch2595@xxxxxxx wrote:

After running the SAVRSTOBJ command from one iSeries to another I'm
seeing many files on that target now with the 0001 extension. Why is
that and how can I avoid that?

The single-value *ALL for the ALWOBJDIF parameter tells the Database Restore feature to preserve the existing data in the file.mbr objects; i.e. to prevent a data-overlay restore. That is effected by renaming the same-named *MEM object or the same-named database *FILE object before restoring the object, if either the Member Level Identifier or the File Level Identifier mismatches between disk and media. Note: These level identifiers can be reviewed using the output of the DSPFD command; at both the system as target of restore and the system as source for the save.

So... Most importantly, do not use the ALWOBJDIF(*ALL). Only ever explicitly specify each of the specific differences that should be allowed during a restore; i.e. even if _all_ of the special values are explicitly included individually. Specifically, the *FILELVL special-value specification for the Allow Object Differences (ALWOBJDIF) parameter should be used if the [File and Member] level identifier differences should be ignored. To be clear, specifying *ALL has a different effect than listing _all_ of the other special values individually.

Otherwise for effecting data-overlay using database restore, those level identifiers are best kept synchronized, such that the deleted [or removed; i.e. RMVM or DLTF] object is performed at the target before the Save\Restore Object (SAVRSTxxx) CL command request.

Regards, Chuck