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



If I understand correctly, you hzve LFs in your custom library over PFs in your standard library.

When you restore the custom library, is the standard library still somewhere in your library list? Taking it out *might* help.

And I seem to recall reading somewhere lately that there was an enhancement in V6R1 to the restore commands that helped in cross library dependency restores.

Sam

On 1/29/2010 11:42 AM, Paul.Wilber@xxxxxxxxxxxxxxxxxxx wrote:

Hi,

We periodically refresh our test environment with production data. We have
a two different data libraries in each environment, one for standard
objects and one for custom objects.
We restore the standard objects first then the custom objects. After the
restore some of the logicals in the test library still point to physicals
in the production library.
We currently have a utility to correct this by using CRTDUPOBJ. We dup from
the production library to a different library, delete the logical in test
and dup the dupped object into test and then delete the previous dupped
object.
Example; Dup logical1 from prod to difflib, dup logical1 from difflib to
test, delete logical1 in difflib.
This corrects the dependancies but is there a way to perform the restore so
that all logicals point to the test library?

Thanks,



paul wilber | sr systems analyst | precision valve corporation


| ( Office: 914.966.4408 | ( Toll free: 800.431.2697 | 2 Fax: 914.966.4630
| * paul.wilber@xxxxxxxxxxxxxxxxxxx



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.