Re: savrstobj questions

On 03 Aug 2012 08:25, fbocch2595@xxxxxxx wrote:

how can I always make sure that the file coming from system A always
gets restored to system B and overlays the file that's on system B?

Only by proper planning. Incompatible changes will be prevented for overlaying data; as a data-only restore, object changes will not be propagated. Most notably, deleted members from system-A will not be reflected on system-B.

The effects should be little different than attempting the same activity between two libraries within the same system using SAVOBJ and RSTOBJ instead of SAVRSTOBJ; excepting where database relations cross libraries, for which the activity on the same system may function but for which restore on a separate system may not function due to missing [or with a newer feature, enabling pending] relations.

I think what you're saying is that if I use *FILELVL then for files
where the File level identifier matches on both systems that file
will be restored from A to B but what option(s) can I use to make
sure a file gets restored from A to B if the File level identifier
does not match?

The *FILELVL special values specified on the ALWOBJDIF parameter tells the Database Restore feature to _Allow_ [the Restore to occur even with File and Member] Object [level identifiers] Differences; i.e. the negation of disallow\prevent of the restore, when differences are found. The parameter could be understood to be an _Ignore_ object differences capability; i.e. allowing the restore, regardless of some differences between the existing object and the object on\being-restored-from the media. Having requested to ignore these object level identifier differences using ALWOBJDIF(*FILELVL), the Database Restore will attempt the data overlay\replacement after further compatibility tests.