×
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.
On 06-May-2014 07:55 -0500, Steinmetz, Paul wrote:
I was considering the restore directly into Lib B, however, I need
review object create dates ensure none are older.
Yes, Lib A is just a holding area, it actually is restored from a
SAVF. <<SNIP>>
FWiW: In some similar tooling I once had written to sanity-check
restoring of a utility library [source and compiled objects] being
developed across a few systems, the SAVLIB request was preceded by a
request to exclusively lock [allow read] the library and then a request
to DSPOBJD The_Lib/*ALL *ALL *FULL OUTPUT(*OUTFILE)
OUTFILE(The_Lib/reserved_name) [and similarly DSPFD requests for member
and record format information] so the details of the objects being saved
would be available wherever the save file was delivered unto which a
RSTLIB might occur to refresh the objects in the same library name on
that target system; i.e. a RSTOBJ of the file(s) of the reserved-names
could be restored first [my tooling restored those object-detail lists
into QTEMP] so object control-level and the various other details could
be compared to decide what\how the restore would transpire [after
optional delete, move, and rename activity against the same-named
objects in the target library before restore, and optional CPYF
FMTOPT(*MAP *DROP) activity to retain system-specific information
because the utility-library did not utilize a separate user-data library].
As an Amazon Associate we earn from qualifying purchases.
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.