× 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.


  1.  Home
  2. MIDRANGE-L
  3. March 2008

Re: PF

I think, Glenn, if the library was saved with the SAVLIB command, all of the logicals will be sequenced on tape so that they restore after their based-upon physical files.

If the files were saved with the SAVOBJ command, however, all bets are off.

Thompson, Glenn wrote:
You sir would be incorrect, at least when saving and restoring from
tape. I'm not arguing for/against the same library stance. Merely
stating the fact.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, March 25, 2008 4:37 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: PF


Untrue. The database restore feature handles proper linkage of LF to

PF, irrespective of file naming, within the same library; i.e. where the

files were all saved in one SAVLIB and being restored as RSTLIB. One RSTLIB will effect the full restore w/out any CPF3204.

Again, the recommendation is to keep the PF & LFs in the same library

because the database /orders/ the restore both for effecting the proper linkage for LF-PF relations and to maximize access path sharing. That ordering is effectively impossible across multiple libraries because the

save of one library is not aware of other libraries, even on the same SAVLIB request -- an over-simplified explanation for a complicated
subject.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.