I have a target zone for each sysres set and a dlib zone for each dlib set. If I need to add maint (even just one ptf) to a res system, but don't want to change an already existing one, I clone the existing sysres set and target zone and zoneedit the pack names. My catalogs are always set up to use ****** and IEASYMxx so that nothing gets messed up.
I maintain lots of sites and literally hundreds of zones this way. When I no longer need one, I scratch the sysres set and the dlib set and delete the zones. It's a pretty solid way to handle things. If anything happens due to maintenance, I always have something to fall back to without having to change anything except the IPL volume and the load parms. Brian On Wed, 13 Mar 2019 18:55:02 +0000, Seymour J Metz <sme...@gmu.edu> wrote: >What happens when you are testing a new service level and you need to install >PTF on the production system? If you apply it to the test system and copy, >then you be running the new service level before you've finished testing it. > > >-- >Shmuel (Seymour J.) Metz >http://mason.gmu.edu/~smetz3 > >________________________________________ >From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of >Carmen Vitullo <cvitu...@hughes.net> >Sent: Wednesday, March 13, 2019 2:24 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: SMPe "rollout" of maintenance > >It really depends, I've never been stuck in a situation when I needed to do >this, if so; > >I'll apply to SMP target, copy to TEST SYSRES, TEST, and move to PROD copied >to the alternate SYSRES. my small 3 LPAR PLEX shares the SYSRES, so migration >is copy to SYSRES(A), IPL test from that SYSRES, TEST, IPL PRODA from >SYSRES(A), IPL PRODB from SYSRES(A). if another ptf is required it will be >applied, and very rare occasions, that SYSRES will be IPL'd in test. then >copied to the OTHER SYSRES SYSRES(B). I've not, so far had a requirement that >I need to maintain a third SYSRES or multiple target zones for the OS > >I am prolly not making this sound easy and not posting this correctly, but I >have a documented process that I've been using for many years that works well, >even in a TEST PLEX / PROD PLEX 6 LPAR environment. >difference now is I have a smaller environment and this methodology lends >itself well to these maint process. >if needed I have a third SYRES available in my back pocket > > >Carmen Vitullo > >----- Original Message ----- > >From: "Seymour J Metz" <sme...@gmu.edu> >To: IBM-MAIN@LISTSERV.UA.EDU >Sent: Wednesday, March 13, 2019 1:09:01 PM >Subject: Re: SMPe "rollout" of maintenance > >That lets you install a PTF on the sysres that matches your target zone, but >what happens if you need the PTF on a different sysres? > > >-- >Shmuel (Seymour J.) Metz >http://mason.gmu.edu/~smetz3 > >________________________________________ >From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of >Carmen Vitullo <cvitu...@hughes.net> >Sent: Wednesday, March 13, 2019 2:03 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: SMPe "rollout" of maintenance > >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 > >---------------------------------------------------------------------- >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 > >---------------------------------------------------------------------- >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
