To expand a bit more on our multi volume respack environment (as Skip points out the biggest challenges were with the wetware and not the technical side). We long ago decided to have minimal entries in the MCAT except for what ware required to be in there OR were on the resvol sets. EVERYTHING on the Resvol sets are cataloged with a symbolic or on 2 specific other packs.
Our maintenance design is to do SMP work in a sandbox environment to the target/dlib datasets which are given Non Mcat Names and exist only in the Maintenance environment (Actually there are 3 sets of these names to reflect the 3 Maintenance environments (Sandbox/Dev/Prod)). From these target libs the running system resvol sets are built using DFDSS doing dataset renames as needed for the include/exclude process. Once IPL'd and tested the active resvol set is then dumped and sent to the next Sysplex for pack builds (as all catalog entries are symbolics no catalog changes are needed). When the resvol set is active in the new Sysplex then the smp target & dlibs are also updated in the original sandbox Maint environment to reflect the running set etc. etc. This allows us to have maint environments that can a) be cloned, b) have 3 concurrent level of any particular set of software at the same time c) apply a PTF to any specific environment as needed without disturbing the other environments. But the real key is to the whole kit & kaboodle that the MCATS only contain symbolics or aliases & then are locked down. Adding new volumes to the set is easy - add a new symbolic. Jerry Whitteridge Manager Mainframe Systems & Storage Albertsons - Safeway Inc. 925 738 9443 Corporate Tieline - 89443 If you feel in control you just aren't going fast enough. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Friday, April 22, 2016 10:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL: Re: Respack Volume Size Challenge After living in close quarters for some time with a single Mod-9 sysres, we seem to have finally outgrown our britches for the next 2.1 RSU. Multiple sysres volumes would require changes to our venerable system migration process, which is used to populate seven different sysplexes from the SMP/E target packs. So we're trying to procure Mod-27s in order not to have to touch the migration mechanism. As Jerry indicates, multiple sysres volumes would require a culture change in addition to a technical one. Bioware is the most difficult area to manage. ;-) BTW the largest allocation on the sysres volume is SCUNTBL, a whopping 2769 cylinders, far larger than distant second SCEERUN2. We could probably stay on a Mod-9 if we treated SCUNTBL as we do ZFS files, which we migrate and manage separately by DSN. Still the simplest solution is a bigger volume. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jerry Whitteridge Sent: Thursday, April 21, 2016 9:02 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: EXTERNAL: Re: Respack Volume Size Challenge We use &SYSR1 through &SYSR5 to have a 5 pack resvol set (note these include OMVS related HFS/ZFS - hence the number/sizes) and have no issues. Biggest problem I have is folks inadvertently recataloging the datasets from their indirect values while doing maintenance so we locked down the Master Cat such that even the Sysprogs have restrictions on what they can change. Jerry Whitteridge Manager Mainframe Systems & Storage Albertsons - Safeway Inc. 925 738 9443 Corporate Tieline - 89443 If you feel in control you just aren't going fast enough. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lucas Rosalen Sent: Thursday, April 21, 2016 2:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL: Re: Respack Volume Size Challenge As far as I have seen, it's quite simple: create a &SYSR2 symbol (using &SYSR1 and changing last char from 1 to 2, for example) and update MCAT accordingly. Once I've worked for a client that had 3-volumes respack. It indeed worked. We used to keep datasets like LINKLIB, MACLIB, NUCLEUS, etc in 1st volumes though... ------------------------------------------------------------------------------------------------------------------------------- *Lucas Rosalen* Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com <lrosa...@br.ibm.com>* LinkedIn: http://br.linkedin.com/in/lrosalen Phone: +48 (71) 792 809 198 2016-04-21 10:45 GMT+02:00 Jake Anderson <justmainfra...@gmail.com>: > Hello, > > From the z/OS 2.1, I have started using Mod-27 as the Load > address(Respack) for IPLing the z/OS 2.1 LPAR. I am curious how the > other Shops are managing when they do not options of using Mod-27 and > they have to survive with Mod-9. I believe the Extended Indirect cataloging > is one Options. > > What kind of challenges are there when the Respack is divided into two > Volumes ? > > Jake ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ________________________________ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
