Re: Disaster Recovery test scenario -- MIDRANGE-L

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

A complicating factor that I encountered once was a client that insistedupon putting the PF's in one library (say, LIBPF) and the logicals inanother library (LIBLF). Obviously, LIBPF would have to be restoredbefore LIBLF. Restore 21 may handle this, or not.

My client actually complicated it further. A had to be restore prior toB; B had to be restored prior to C; C had to be restored prior to A!For the life of me right now I can't remember what we did. But to thisday, except for fly-by-night LF's in QTEMP, I insist that logicals be inthe same library as the physicals. Joins could complicate that, but sofar I haven't had physicals in multiple libraries for a join - yet.




        * Jerry C. Adams
*iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.893.8633x152
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Rick Aguiar wrote:

The only impact I've seen is where objects are not named with the library so
you may need to restore some libraries again based on the name of the lib
versus object.

You can also just do the 21 restore process which takes all the single steps
out of the process.
Rick

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.