On Sat, 12 Jan 2008 22:55:51 -0800, Edward Jaffe wrote: > >SMP/E is too efficient! It's design point is, when performing a "mass" >apply of hundreds (or even thousands) of PTFs, that it installs only the >highest level of each element being replaced. Intermediate levels are >neither created nor journaled. There is no version to "undo" to! > Hmmm. If it kept no such journal, it wouldn't be able to warn you or stop you, which I believe it does (somewhat guessing -- I haven't tried an experiment) when you RESTORE a PTF without also RESTOREing intermediate, non-ACCEPTed, levels containing common elements.
>Backing off any one PTF requires a RESTORE (from DLIB) of all elements, >from all interdependent PTFs, followed by re-APPLY specifying EXCLUDE >for the "problem" PTF. Granted, it would be nice if more of this >processing could be performed automatically. > Indeed. As for how much you keep (Ed G.'s concern?), when you're sure, do an ACCEPT PURGE. Everything newer that is available in the GLOBAL zone, which is the reason it's possible to perform the RESTORE; APPLY EXCLUDE operation you describe above. Hmmm. I suspect I can't RESTORE a SUPerseded PTF. But can I RESTORE then APPLY EXCLUDE it and expect that the SUPerseding PTF will not be APPLYed? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
