× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You can get the messages right from the local job log. No errors recorded, it successfully restored. If there is an error, then you have to start a session on the remote machine to pull the exact job log messages. Not trivial to do programmatically but very doable since you will know the job information that started on the remote box. Once you start the session on the remote system pull the file information and compare it to the local.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 8/3/2012 10:25 AM, fbocch2595@xxxxxxx wrote:
Thanks Chuck/Vern, etc. but 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? 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?
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
-

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.