You could also accomplish much the same thing by moving all of your user data libraries into IASPs.
Then, issue SETASPGRP to change to a different ASP group, and restore the objects into libraries with the same names, and then rename those libraries after the restore, then save them again, to allow restoring those new library names in the original "disk pool" (aka. ASP group). (It is a fair amount of work to set up that infrastructure, but not quite as much as a full-blown LPAR.)
You might also want to consider "omitting" those join LFs on the SAVLIB or SAVOBJ command, so they will simply not be involved in the RSTLIB or RSTOBJ process at all? (See the OMITOBJ parameter on SAVLIB and SAVOBJ ...) Then, just recreate them from source (DDS or DDL) after that?
All the best,
Mark S. Waterbury
On Wednesday, January 8, 2020, 10:36:57 AM EST, Rob Berendt <rob@xxxxxxxxx> wrote:
Well, you could create a separate test/development lpar and restore them there with the same name.
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Cross-library Logicals and RSTLIB/CRTDUPOBJ, (continued)
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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.