×
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.
On 19 Jul 2012 08:22, Vern Hamberg wrote:
SAVRSTOBJ is mostly just like SAVOBJ and RSTOBJ on a single system.
How a restore works with LFs is the same as RSTOBJ. If you specify
only the PFs, that's all you get on the other side - unless you say
ACCPTH(*YES), right? You don't have to name the LFs in that case,
IIRC.
What is both desired and effected make all the difference with regard
to use of the Access Path parameter.
If the attempt is to effect data restore only, overlaying existing
data in any physical file member(s), then saving access paths is
worthwhile; i.e. the logical files presumably already exist at the
target for the restore. If restoring objects, then the logical files
must be included [e.g. by name] in the save. Saved access paths will be
restored\associated with either restored or existing logical file
member(s) [that have the same AccPth level identifier], but merely
requesting to save the access paths over the data does not effect the
save [thus also not the restore] of the logical files\members [the
objects] that defined each [LFM] access path.
Regards, Chuck
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.
midrange.com
