Re: savrstobj questions

[Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>]

You would specify ALWOBJDIF(*FILELVL) to force the system to lay down 
the file even if the file level IDs are not the same.  The same rule for 
any other restore command.

I'd still check the messages though, there are several things you can 
monitor for.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 8/3/2012 11:49 AM, fbocch2595@xxxxxxx wrote:
> Hi Jim.  Actually, I was asking what the syntax would be on the savrstobj command.
> Frank
>
>
> -----Original Message-----
> From: Jim Oberholtzer<midrangel@xxxxxxxxxxxxxxxxx>
> To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>
> Sent: Fri, Aug 3, 2012 11:50 am
> Subject: Re: savrstobj questions
>
>
> You can get the messages right from the local job log.  No errors
> ecorded, it successfully restored.  If there is an error, then you have
> o start a session on the remote machine to pull the exact job log
> essages.  Not trivial to do programmatically but very doable since you
> ill know the job information that started on the remote box.  Once you
> tart the session on the remote system pull the file information and
> ompare it to the local.
> Jim Oberholtzer
> hief Technical Architect
> gile Technology Architects
>
> n 8/3/2012 10:25 AM,fbocch2595@xxxxxxx  wrote:
>   Thanks Chuck/Vern, etc. but how can I always make sure that the file coming
> rom system A always gets restored to system B and overlays the file that's on
> ystem B?  I think what you're saying is that if I use *FILELVL then for files
> here the File level identifier matches on both systems that file will be
> estored from A to B but what option(s) can I use to make sure a file gets
> estored from A to B if the  File level identifier does not match?
>   Thanks, Frank
>
>
>
>   -----Original Message-----
>   From: CRPence<CRPbottle@xxxxxxxxx>
>   To: midrange-l<midrange-l@xxxxxxxxxxxx>
>   Sent: Thu, Aug 2, 2012 5:26 pm
>   Subject: 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
>   estore feature to preserve the existing data in the file.mbr objects;
>   .e. to prevent a data-overlay restore.  That is effected by renaming
>   he same-named *MEM object or the same-named database *FILE object
>   efore restoring the object, if either the Member Level Identifier or
>   he File Level Identifier mismatches between disk and media.  Note:
>   hese level identifiers can be reviewed using the output of the DSPFD
>   ommand; at both the system as target of restore and the system as
>   ource for the save.
>       So... Most importantly, do not use the ALWOBJDIF(*ALL).  Only ever
>   xplicitly specify each of the specific differences that should be
>   llowed during a restore; i.e. even if_all_  of the special values are
>   xplicitly included individually.  Specifically, the *FILELVL
>   pecial-value specification for the Allow Object Differences (ALWOBJDIF)
>   arameter should be used if the [File and Member] level identifier
>   ifferences should be ignored.  To be clear, specifying *ALL has a
>   ifferent effect than listing_all_  of the other special values
>   ndividually.
>       Otherwise for effecting data-overlay using database restore, those
>   evel identifiers are best kept synchronized, such that the deleted [or
>   emoved; i.e. RMVM or DLTF] object is performed at the target before the
>   ave\Restore Object (SAVRSTxxx) CL command request.
>   Regards, Chuck
>   -
> -