I've seen so many different ways to do this, for me they easiest way; I maintain one CSI for ZOS, and one target zone, I maintain different levels of the base/maint on different SYSRES volumes, give me a way back if needed and the ability to apply those one-off's and test and move to an alternate SYSRES. much more to it but I think you get the point. everything I apply and copy is kept updated in an Excel spreadsheet
Carmen Vitullo ----- Original Message ----- From: "Tom Marchant" <0000000a2a8c2020-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Wednesday, March 13, 2019 12:53:16 PM Subject: Re: SMPe "rollout" of maintenance On Wed, 13 Mar 2019 12:30:35 -0500, Bill Giannelli <billgianne...@gmail.com> wrote: >When I obtain maintenance for an RSU (e.i. for Db2 RSU1902). >I receive and apply, then implement first in one of our 2 sand boxes, leaving >our 2nd sand box at our prior maintenance level. >My question is, before I have rolled out the new maintenance, what if I need a >one off PTF for the prior maintenance? >Should 2 CSIs be kept? One for new maintenance and a second one for a prior >maintenance level. Others have different ideas about how to manage your target zones. My preference is to always clone a new Target and distribution zone before applying maintenance. When a Target zone is no longer needed i.e. there is no system running that level of the code and there is no need to go back, the old zones can be deleted. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
