One Global, two Targets, one DLIB, that's what I've done in a previous shop, for products only,that was the standard, the target zone was named for the sysplex, and the DDDEF's reflected the Plex name in the target datasets in that zone, so my plex name was PLEX1 lets say, so my zone names were TPLEX1 and TPLEX2, for example, and the target dataset names were some hlq.vendor.product.TPLEX1 or 2. dsntype. like I said that was a standard at this shop, we maintained a PROGxx member for each system in the PLEX, if APF is required both PLEX1 and PLEX2 are listed, when applying maint in each system that systems PROG00 linklist or other places were updated to the currently applied target library. I would only apply to the second zone once 1) the maint made it around the PLEX, 2) no issues were found during testing/prod, so one receive, 2 applies, 1 accept.
everyone has their favorite way of maintaining a system or product, some because that's how they learned, some because they developed a methodology that works well for them that will provide the ability to maintain the system or product, provide an easy backout if problems and an easy was to clone (if necessary). I've worked with and for Global Services the way we maintained a customer site was very much different than another outsourcer I worked for, and much different that the site I'm currently working at, right or wrong, it's the way that works for me, and I've documented the process from receiving a new order, to installing that order thru migration and maint process. think 1980's, that's what I came into all system catalogs were on the sysres, all uss HFS and ZFS were on the sysres, sys1.proclib, and sys1.ibm.proclib ,sys1.parmlib, and sys1.ibm.parmlib , no iplparm :( so each library was modified for each system so caution was required when merging the updates from the order libraries. Carmen Vitullo ----- Original Message ----- From: "william giannelli" <billgianne...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Thursday, March 14, 2019 7:25:44 AM Subject: Re: cloning target and dlib zones so for each cloned target I need a separate CSI? On Thu, Mar 14, 2019 at 8:20 AM Jake Anderson <justmainfra...@gmail.com> wrote: > I usually keep 4 different sets of target CSI and Just one DLIB(As we > accept the previous maintenance only when the previous maintenance has > baked for some time ) > > TG1,TG2,TG3,TG4. > > So on the cloning process one qualifier matching to CSI name .. > > > > On Thu, 14 Mar, 2019, 3:08 PM Bill Giannelli, <billgianne...@gmail.com> > wrote: > > > to maintain 2 different maintenance levels I want to clone my target and > > dlib. would this require 2 separate CSIs? And would I have to 2 copies of > > most of the dddefs? > > 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 > ---------------------------------------------------------------------- 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
