|
To qualify, I am not real knowledgeable on BRMS. I was only offering suggestion on how to get around the "Q" library issue. Now you did write: > When you have to recover a whole machine you will first build the > system from your system save, media or whatever your plan is, then > RSTUSRPRF etc. How would you know what tape to load to restore that info?? Maybe you save the BRMS save files to the same tape. Does anybody know what IBM's recommendation is for this situation?? ---------------------------- Bryan Dietz Aktion Associates midrange-l-bounces@xxxxxxxxxxxx wrote on 08/24/2005 03:26:28 PM: > Hi Bryan > > I think the books point out that this is not a good idea. The reason > (as I understand it) is as follows: > > When you have to recover a whole machine you will first build the > system from your system save, media or whatever your plan is, then > RSTUSRPRF etc. > > Following this, when the base operating system is built you will > restore QUSRBRM (or use the latest SAVMEDIBRM data to update it) so > that you can restore data from TSM. QUSRBRM contains the data to know > how to get to TSM and also where all the data is stored in TSM. > Without QUSRBRM you have know way of knowing where in TSM the data is stored. > > If you have a save file that contains all the data about where the > data is saved in TSM, but it itself is saved in TSM, how are you > going to find it in order to restore it ? It's kind of like locking > the combination to a safe inside the safe for security but not > writing it down anywhere else. > > There are a couple of other things this applies to as well like user > profiles, QGPL and QUSRSYS. > > At least that's how I understand it. If there's something I've missed > somewhere along the way and you've been able to make this work in a > real recovery scenario then I'd love to hear it. > > Regards > Evan Harris
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.