Joe,

If the restore library contain the PF is different than the source library, it won't work, even with using DFRID.
That is why I had to keep the libraries with PF the same name, then rename.

Also, any x-lib access path cannot be saved (access paths can only be saved if the LF and PF exist in the same library), and they must be rebuilt after the restore.

Paul


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Joe Pluta
Sent: Wednesday, January 08, 2020 10:00 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Cross-library Logicals and RSTLIB/CRTDUPOBJ

Thanks, Paul!  That's the direction I was headed until I read Mark's excellent note on DFRID.  I'm going to try that right now.

On 1/8/2020 8:45 AM, Steinmetz, Paul via MIDRANGE-L wrote:
Joe,

We restore our Production data to R&D data on a different LPAR.
The R&D data has different library names.
To handle the x-lib LF when the restore library is different (without
having to recreate) The libraries containing the PF are restored with the same library names.
Then the libraries containing the X-lib LF are restored.
Then the libraries containing the PF are renamed.

Totally automated using AJS and BRMS.
Works like a champ.

Also, starting at V6R1, IBM built in DFRID on the RSTLIB and RSTLIBBRM command.
Using DFRID to Allow Restoring Logical Files before Physical Files
https://www.ibm.com/support/pages/using-dfrid-allow-restoring-logical-
files-physical-files

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzarm/rzarmse
qrestoredeferobject.htm

Paul


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Joe Pluta
Sent: Wednesday, January 08, 2020 9:21 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Cross-library Logicals and RSTLIB/CRTDUPOBJ

Has anyone ever identified a process to handle either RSTLIB or CRTDUPOBJ for cross-library logicals: those pesky logical files that join physical files in two different libraries (they can also be created as SQL VIEWs these days).

The problem is simple.  I can create a logical ABC1/LF over ABC1/PF and ABC2/PF.  But if I save and restore those libraries to a different name (say XYZ1 and XYZ2), I end up with a "broken" logical.  XYZ1/LF ends up being created over XYZ1/PF and ABC2/PF.   The same happens if I try to do a CRTDUPOBJ of ABC1/LF to XYZ1/LF.

I have found no way short of recreating the logical file with CRTLF (or RUNSQLSTM for a VIEW) to link the logical correctly to both physicals.

This has been a problem for 30 years, which is why I've since avoided
them like the plague.  But I have a few of them I'm dealing with right
now and they're quite annoying, and I was hoping something had changed
over the years.  :)

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

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