Re: SMPe "rollout" of maintenance
We have needed to manage/maintain multiple releases of "MVS" for decades. We always create a new CSI for each release and tie all components to that CSI with DSN qualifier(s). There is NO mix-n-match. The main motivator is that while a CSI can have multiple TARGET and DLIB zones, it can have only one GLOBAL zone. For any given APAR, two different z/OS releases may or may not get multiple PTFs depending on FMID: not all components are necessarily updated in each z/OS package. Moreover, we install each ServerPac into its own CSI. With multiple sysprogs doing the work, I can't imagine mushing different releases into a single CSI. OTOH we stick with a single CSI throughout the life of a single release. PTFs get installed in one place. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Thursday, March 14, 2019 10:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SMPe "rollout" of maintenance That's how I like to operate, with one variation: I prefer to rotate among sysres sets rather than cloning and deleting, and I don't dedicate a sysres set to one LPAR except when I'm in the process of promoting a testing a new level. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Thursday, March 14, 2019 4:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMPe "rollout" of maintenance 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 +, Seymour J Metz 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 on >behalf of Carmen Vitullo >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" >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 on >behalf of Carmen Vitullo >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 ab
Re: SMPe "rollout" of maintenance
That's how I like to operate, with one variation: I prefer to rotate among sysres sets rather than cloning and deleting, and I don't dedicate a sysres set to one LPAR except when I'm in the process of promoting a testing a new level. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Thursday, March 14, 2019 4:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMPe "rollout" of maintenance 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 +, Seymour J Metz 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 on behalf of >Carmen Vitullo >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" >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 on behalf of >Carmen Vitullo >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" <000a2a8c2020-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 >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.
Re: SMPe "rollout" of maintenance
I should have mentioned that I also have a single global zone for everything at that particular site. The only time I change global zones is when I install a new OS release. It's not that I have to, I just do it that way so that I don't get things mixed up. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPe "rollout" of maintenance
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 +, Seymour J Metz 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 on behalf of >Carmen Vitullo >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" >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 on behalf of >Carmen Vitullo >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" <000a2a8c2020-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 >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 acc
Re: SMPe "rollout" of maintenance
On Wed, 13 Mar 2019 13:09:03 -0500, Bill Giannelli wrote: >Please excuse the rookie questions, but that means one global, clone the >target and dlib before apply. >then lets say I need a one-off ptf to the previous maintenance levelI >apply that to the clone target? >thanks Yes, one global zone. When cloning the target zone, o ZONECOPY to copy the zone o ZONEEDIT to update DDDEFs o Use your favorite tool to copy the data sets. DSS, FDRCOPY, etc. If you are going to do it this way, I suggest a naming convention that will help you to keep it straight. For z/OS that might be o Target zone name is Tvolser or volserT o DLIB zone name Dvolser or volserD where "volser" is the name of the IPL volume. For other products, the target zone name can be one node of the DSNAME of the target data sets. You can use SYMBOLICRELATE to define data set aliases, then change to a different release by updating the symbol for that product. If the product has a started task, you will need to shut down the product, change the symbol, and bring the started task back up. For linklist data sets, specify the symbol in the data set name in your PRODxx for IPL time. For dynamic changes, define a new linklist set after shutting down any started tasks that use the product, then bring it back up. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPe "rollout" of maintenance
I typically apply maintenance to my base target zone which has an associated DLIB zone which is never IPLed from. I have 3 SYSRES volumes per environment (TECH, DEV, PROD-A, PROD-B) for a total of 12 SYSRES volumes. I have a cloning process that besides building the entire sysres, also does a full SMPE ZONECOPY to match it, and is connected to the common Global. At any time, I have a complete and in-tact SMPE environment to match every SYSRES.This has been helpful for IBM support wanting to know a PTF Level of a particular module, to applying the PTF in a pinch(very rare), etc. _ Dave Jousma Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Bill Giannelli Sent: Wednesday, March 13, 2019 1:31 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMPe "rollout" of maintenance **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** 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. Thanks Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMPe "rollout" of maintenance
Nothing ever goes to prod unless its not thru the migration process, if a PTF is needed for prod and our sandbox is not fully tested (which has not happened) it gets applied to the test lpar's sysres. I understand the scenario you're talking about, I've just never had the need to apply a PTF on PROD without going to test first. time is on my side, my team tests as soon as I IPL the test system (sandbox), so that scenario has not happened, and I'm prepared to move that service to prod, with a needed PTF. and again, it all depends on what the specific PTF touches, some are compile lib update, mac updates, rexx.so many different scenarios I don't roll out maint or service levels but once or twice a year, that's mandated by leadership, so maybe 4 IPL's per year, RSU at 6 month intervals , and RSU+TOLERATION before I freeze the systems and start the next ServerPac install I can't speak to every scenario, but again, at this small site with mainframe going away and more and more distributed applications, this process works well. so I guess, I'll keep my fingers crossed behind my back and say "I've never had to apply an emergency PTF" on top of a prod system when my latest RSU level is still being tested. Carmen Vitullo - Original Message - From: "Seymour J Metz" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Wednesday, March 13, 2019 1:55:02 PM Subject: Re: SMPe "rollout" of maintenance 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 on behalf of Carmen Vitullo 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" 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 on behalf of Carmen Vitullo 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" <000a2a8c2020-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 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 a
Re: SMPe "rollout" of maintenance
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 on behalf of Carmen Vitullo 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" 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 on behalf of Carmen Vitullo 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" <000a2a8c2020-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 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
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" 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 on behalf of Carmen Vitullo 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" <000a2a8c2020-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 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
Re: SMPe "rollout" of maintenance
You apply the PTF to whichever target zone(s) you need it on. You might apply it to one, test it and then apply it to another, or you might only need it one the first target zone you update. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Bill Giannelli Sent: Wednesday, March 13, 2019 2:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMPe "rollout" of maintenance thanks for the reply! Please excuse the rookie questions, but that means one global, clone the target and dlib before apply. then lets say I need a one-off ptf to the previous maintenance levelI apply that to the clone target? thanks Bill -- 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
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 on behalf of Carmen Vitullo 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" <000a2a8c2020-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 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
Re: SMPe "rollout" of maintenance
thanks for the reply! Please excuse the rookie questions, but that means one global, clone the target and dlib before apply. then lets say I need a one-off ptf to the previous maintenance levelI apply that to the clone target? thanks Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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" <000a2a8c2020-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 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
Re: SMPe "rollout" of maintenance
On Wed, 13 Mar 2019 12:30:35 -0500, Bill Giannelli 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
Re: SMPe "rollout" of maintenance
Always have a CSI for any instance of a package serviced by SMP. Depending on your methodology you may have several large CSIs or many smaller ones, but you dhould have a taqrget and dlib zone for each instance. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Bill Giannelli Sent: Wednesday, March 13, 2019 1:30 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMPe "rollout" of maintenance 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. Thanks Bill -- 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
SMPe "rollout" of maintenance
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. Thanks Bill -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
