|
-----Original Message----- From: Bale, Dan <D.Bale@handleman.com> To: midrange-l@midrange.com <midrange-l@midrange.com> Date: Thursday, August 23, 2001 9:57 AM Subject: RE: APYJRNCHG >After restoring Monday night's SAVCHGOBJ, we determined yesterday that >FILE123 would still be on the system, even though it was deleted on >Monday. When we restore Tuesday night's SAVCHGOBJ, will the restore >balk at restoring an object that it shows having a creation date after >the one found on the system (restored from the Sunday night backup)? >How about other object attributes? A change in the record format? Yes. That's what the allow object differences parameter is for. Without this parameter set to *ALL, then the restore refuses because of the levels. With it set renamed duplicates can appear. >Another scenario... Logical files. If you were restoring a bunch of >incremental backups, would you have the option to specify that (and I'd >guess this would only apply if you used the default ACCPTH(*NO) on your >saves) access paths not be rebuilt for all but the last restore? It >seems almost mandatory that if your recovery plan includes restoring >from incremental backups, you'd better be saving your access paths. The way to do that is set them for rebuild on open and then override that at the end of the restore with the WRKAPRCY or whatever that command is.... I'm not on a machine right now... =========================================================== R. Bruce Hoffman, Jr. -- IBM Certified Specialist - AS/400 Administrator -- IBM Certified Specialist - RPG IV Developer "America is the land that fought for freedom and then began passing laws to get rid of it." - Alfred E. Neuman
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.