In a recent note, David Cole said: > Date: Wed, 13 Sep 2006 14:13:56 -0400 > > At 9/13/2006 01:30 PM, TMerchant wrote: > >But why does it require that previously received maintenance be > >REJECTed and that previously APPLY'ed maintenance be RESTORed? > > Because our maintenance is cumulative, not incremental. > - That means that the latest maintenance file always > contains all maintenance, not just the most recent. > - That means that the file as a whole has to be APPLY'd to > the instance of the product that existed immediately > after initial install. > - That means that all prior maintenance has to be removed > before the new maintenance file can be successfully > APPLY'd. > - And that's what RESTORE and REJECT do. > - And that's why our canned maintenance JCL contains > RESTORE, REJECT, RECEIVE and APPLY, in that order. > In other words, the process is fully automated by a > single job. > Wouldn't SUPersede with element replacements accomplish the same thing? (I know SUPersede is no good for ZAPs and IEBUPDTEs -- BTDTGTS. DLI. NGDIA.)
-- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
