I've never seen the logic behind delaying the acceptance of a large round of maintenance, say a quarterly RSU application. Since PTF chains are usually very long, the ability to RESTORE a single PTF becomes a daunting, if not impossible task. If there is a problem after a large maintenance run, you're better off trying to find a fix for your problem than attempting to RESTORE the 'bad' PTF. That's assuming of course that you stay a quarter or two back-level in your RSU installations.
Hence, for large maintenance runs, I usually do an ACCEPT run a week or so after the APPLY. I see no advantage in delaying it. On Fri, Jul 17, 2009 at 1:31 PM, Rick Fochtman <[email protected]> wrote: > Chase, John wrote: > > -----Original Message----- >>> From: IBM Mainframe Discussion List On Behalf Of Klein, Kenneth >>> >>> In today's environment and IBM's ever changing methods of >>> delivering/offering maintenance and upgrades to z/OS - what are your >>> common best practices? >>> Before every APPLY? >>> Never? >>> >>> >> >> Our general ROT is to ACCEPT PTFs that have been running in the >> production environment for 3 months or longer before APPLYing the "next >> round" of preventive maintenance. APARs and USERMODs are *NEVER* >> ACCEPTed. >> >> -jc- >> >> > ------------------------------------<unsnip>---------------------------- > Pretty much the same attitude here. One variation: we don't apply APARs > unless the need is severe and immediate; we'd rather wait for the PTF. > > Rick > > ---------------------------------------------------------------------- > 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 > -- Guy Gardoit z/OS Systems Programming ---------------------------------------------------------------------- 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
