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
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,
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.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.