Re: Better support for multiple master catalogs in a sysplex
Lennie, I can appreciate your RFE, we used to maintain multiple mastercat’s in our prod sysplex, but do not anymore.Mostly due to the extra efforts and issues you note in your RFE. Our OMVS and CSF datasets are in usercats.We do take catalog backups 4 times a day, and our master catalog is pretty stable, as in the contents of it doesn’t change much. As for your highlights of certain products that are or could be VSAM, we do isolate some of those items into their own USERCAT so that we can have stricter access rules for those catalogs (general public doesn’t have update access). We also happened to be a GDPS customer, so we have isolated K systems connected to the sysplex where we could do the necessary repairs if it ever came to that. While not all shops are GDPS, the idea remains similar in that you could have another disconnected lpar with access to the DASD (but offline), to do any kind of necessary recovery. Dave Jousma Vice President | Director, Technology Engineering From: IBM Mainframe Discussion List on behalf of Lennie Dymoke-Bradshaw <032fff1be9b4-dmarc-requ...@listserv.ua.edu> Date: Monday, November 6, 2023 at 8:02 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Better support for multiple master catalogs in a sysplex I have just raised an RFE regarding support for better sharing of VSAM system datasets (such as RACF, ICSF key stores and ZFS file systems) when used in a sysplex with multiple master catalogs. Please would you examine it and support of relevant I have just raised an RFE regarding support for better sharing of VSAM system datasets (such as RACF, ICSF key stores and ZFS file systems) when used in a sysplex with multiple master catalogs. Please would you examine it and support of relevant for you. https://urldefense.com/v3/__https://ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-3890__;!!MwwqYLOC6b6whF7V!gDErcwuVzIRgwvRCcZtGPvKZe2wgGAOI3fK9vJWOm4eIrdxXqqQAsa01MoMDrNecT1BKVhVLI0_KyZu2WrJ83n211Cr90JjJM28$<https://urldefense.com/v3/__https:/ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-3890__;!!MwwqYLOC6b6whF7V!gDErcwuVzIRgwvRCcZtGPvKZe2wgGAOI3fK9vJWOm4eIrdxXqqQAsa01MoMDrNecT1BKVhVLI0_KyZu2WrJ83n211Cr90JjJM28$> Thanks Lennie Dymoke-Bradshaw https://urldefense.com/v3/__https://rsclweb.com__;!!MwwqYLOC6b6whF7V!gDErcwuVzIRgwvRCcZtGPvKZe2wgGAOI3fK9vJWOm4eIrdxXqqQAsa01MoMDrNecT1BKVhVLI0_KyZu2WrJ83n211Cr9tuyN6c4$<https://urldefense.com/v3/__https:/rsclweb.com__;!!MwwqYLOC6b6whF7V!gDErcwuVzIRgwvRCcZtGPvKZe2wgGAOI3fK9vJWOm4eIrdxXqqQAsa01MoMDrNecT1BKVhVLI0_KyZu2WrJ83n211Cr9tuyN6c4$> <https://urldefense.com/v3/__https://rsclweb.com/__;!!MwwqYLOC6b6whF7V!gDErcwuVzIRgwvRCcZtGPvKZe2wgGAOI3fK9vJWOm4eIrdxXqqQAsa01MoMDrNecT1BKVhVLI0_KyZu2WrJ83n211Cr9GwIOX3Q$<https://urldefense.com/v3/__https:/rsclweb.com/__;!!MwwqYLOC6b6whF7V!gDErcwuVzIRgwvRCcZtGPvKZe2wgGAOI3fK9vJWOm4eIrdxXqqQAsa01MoMDrNecT1BKVhVLI0_KyZu2WrJ83n211Cr9GwIOX3Q$>> 'Dance like no one is watching. Encrypt like everyone is.' -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN 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
Better support for multiple master catalogs in a sysplex
I have just raised an RFE regarding support for better sharing of VSAM system datasets (such as RACF, ICSF key stores and ZFS file systems) when used in a sysplex with multiple master catalogs. Please would you examine it and support of relevant for you. https://ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-3890 Thanks Lennie Dymoke-Bradshaw https://rsclweb.com <https://rsclweb.com/> 'Dance like no one is watching. Encrypt like everyone is.' -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Better support for multiple master catalogs in a sysplex
I have just raised an RFE regarding support for better sharing of VSAM system datasets (such as RACF, ICSF key stores and ZFS file systems) when used in a sysplex with multiple master catalogs. Please would you examine it and support of relevant for you. Thanks Lennie Dymoke-Bradshaw https://rsclweb.com <https://rsclweb.com/> 'Dance like no one is watching. Encrypt like everyone is.' -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in parallel sysplex ECS vs RLS
Thank-you all for your responses. Again the IBM-Main community shows it's strength. I think I'll be sticking with ECS at the moment. Much appreciated, Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in parallel sysplex ECS vs RLS
>While RLS catalog sharing require more effort to establish, it wasn't >introduced just for fun. It seems customers needed some enhancement over >ECS. IIRC from the course, it was for performance reasons. RSL provides better performance for heavily used catalogs. Met vriendelijke groet, Kees Vernooij KLM Information Services z/OS Systems Tel +31 6 10 14 58 78 -Original Message- From: IBM Mainframe Discussion List On Behalf Of R.S. Sent: 24 April 2020 11:20 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in parallel sysplex ECS vs RLS W dniu 23.04.2020 o 16:29, Peter Vander Woude pisze: > Ok, building parallel sysplex. For the catalogs I am planning on using ECS > for the shared catalogs (which is all of them). > > What is the recommended method for handling the catalogs in a parallel > sysplex, ECS or VSAM RLS? What is recommended method? It depends. :-) WHAT DO YOU NEED? "Legacy" catalog sharing is worse than ECS. ECS is relatively easy to implement. However many years later IBM introduced catalog sharing with RLS. It is more effective for extensive sharing of given BCS, however Master Catalog cannot be shared that way. While RLS catalog sharing require more effort to establish, it wasn't introduced just for fun. It seems customers needed some enhancement over ECS. Again, YMMV, we don't know your workload, etc. If you are starting with that, think about VLF (it's not related to sharing), then ECS. However if you are using RLS, you have the infrastructure up and ready, so RLS catalog sharing seem to be low hanging fruit. Last, but not least: sharing outside sysplex is completely different animal, and you should avoid it as possible. In that case absolutely don't try to use ECS or RLS. -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 169.401.468 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169.401.468 as at 1 January 2020. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in parallel sysplex ECS vs RLS
W dniu 23.04.2020 o 16:29, Peter Vander Woude pisze: Ok, building parallel sysplex. For the catalogs I am planning on using ECS for the shared catalogs (which is all of them). What is the recommended method for handling the catalogs in a parallel sysplex, ECS or VSAM RLS? What is recommended method? It depends. :-) WHAT DO YOU NEED? "Legacy" catalog sharing is worse than ECS. ECS is relatively easy to implement. However many years later IBM introduced catalog sharing with RLS. It is more effective for extensive sharing of given BCS, however Master Catalog cannot be shared that way. While RLS catalog sharing require more effort to establish, it wasn't introduced just for fun. It seems customers needed some enhancement over ECS. Again, YMMV, we don't know your workload, etc. If you are starting with that, think about VLF (it's not related to sharing), then ECS. However if you are using RLS, you have the infrastructure up and ready, so RLS catalog sharing seem to be low hanging fruit. Last, but not least: sharing outside sysplex is completely different animal, and you should avoid it as possible. In that case absolutely don't try to use ECS or RLS. -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 169.401.468 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169.401.468 as at 1 January 2020. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in parallel sysplex ECS vs RLS
I recall from a z/OS update course, a couple of years ago already, the recommendation that RLS for Catalogs was the way to go. Kees. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Peter Vander Woude Sent: 23 April 2020 16:29 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalogs in parallel sysplex ECS vs RLS Ok, building parallel sysplex. For the catalogs I am planning on using ECS for the shared catalogs (which is all of them). What is the recommended method for handling the catalogs in a parallel sysplex, ECS or VSAM RLS? Thanks, Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in parallel sysplex ECS vs RLS
One or the other, not both. It's OK to use either/or on a catalog by catalog basis, but you cannot double down. Reference z/OS 2.2.0 DFSMS Managing Catalogs - Accessing Catalogs for Record Level Sharing, Restrictions: * Master catalogs are currently not supported in RLS mode. Ensure that any catalog in RLS mode is not being shared as a master catalog by any system in the plex. * RLS protocol cannot be used simultaneously with either ECS or VVDS protocol for a catalog. This is enforced by the SMSVSAM address space. If you attempt to use a catalog currently in RLS mode from a non-RLS system in the sysplex, the associated catalog request will fail with return code RC4 and reason code RSN124. If a catalog is currently in either ECS mode or VVDS mode and is shared by a system that cannot support RLS for catalogs, the attempt to use the catalog in RLS mode will also fail with return code RC4 and reason code RSN124. To place a catalog in RLS, it must be SMS-managed, and the SMSVSAM server must be active on all systems in the sysplex. You can move a catalog in and out or RLS mode with RLSQUIESCE and RLSENABLE, for emergency or maintenance purposes, but it's not recommended to do so frequently. We put all of our user catalogs in RLS, except for two specific catalogs with system-critical dataset entries, that don't get hit that often. These are in VLF. RLS seems to be the better performing option for us. Art Gutowski General Motors, LLC On Thu, 23 Apr 2020 16:43:44 +, Allan Staller wrote: >ITYM ECS. (Enahnced Catalog Sharing). > >ECS is specific to catalogs and uses a structure for inter-image communication. >RLS uses a local address space (SMSVSAM) for local communication AND a >structure for inter-image communication. > >Both are performance related. > >IMO, RLS is more appropriate for applications. ECS is less overhead. > >ECS should be sufficient for most purposes. I have not researched the >practicality or mpact of attempting both on the same catalog (KSDS). > >-Origanal Message- >From: IBM Mainframe Discussion List On Behalf Of >Peter Vander Woude >Sent: Thursday, April 23, 2020 9:29 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Catalogs in parallel sysplex ECS vs RLS > >Ok, building parallel sysplex. Forhthe catalogs I am planning on using ECS >for the shared catalogs (which is all of them). > >What is the recommended method for handling the catalogs in a parallel >sysplex, ECS or VSAM RLS? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in parallel sysplex ECS vs RLS
ITYM ECS. (Enahnced Catalog Sharing). ECS is specific to catalogs and uses a structure for inter-image communication. RLS uses a local address space (SMSVSAM) for local communication AND a structure for inter-image communication. Both are performance related. IMO, RLS is more appropriate for applications. ECS is less overhead. ECS should be sufficient for most purposes. I have not researched the practicality or mpact of attempting both on the same catalog (KSDS). HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Peter Vander Woude Sent: Thursday, April 23, 2020 9:29 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalogs in parallel sysplex ECS vs RLS [CAUTION: This Email is from outside the Organization. Do not click links or open attachments unless you trust the sender.] Ok, building parallel sysplex. For the catalogs I am planning on using ECS for the shared catalogs (which is all of them). What is the recommended method for handling the catalogs in a parallel sysplex, ECS or VSAM RLS? Thanks, Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Catalogs in parallel sysplex ECS vs RLS
Ok, building parallel sysplex. For the catalogs I am planning on using ECS for the shared catalogs (which is all of them). What is the recommended method for handling the catalogs in a parallel sysplex, ECS or VSAM RLS? Thanks, Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
Ken, All SYSRES datasets, except for SYS1, are in the catalog on the SYSRES. Aliases are symbolics pointing to CATALOG.SOFTWARE. SYS1 datasets are in MCAT with a volser of **. MCAT is on a sysplex level volume and shared across the LPARs in the plex. Maintenance and upgrades are installed in a sandbox environment. All SMP work is done only there. Once a month we clone the sandbox SYSRES volume and roll it into test and prod (the actual SYSRES volser changes every month). Sorry for not being clear on the MCAT part before. Bart -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ken Smith Sent: Thursday, December 01, 2016 12:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX I'd still like to know how this works. What's in your master cat? What's in your sysres cat? Ken On Tue, Nov 22, 2016 at 11:28 AM, van der Grijn, Bart (B) < bvandergr...@dow.com> wrote: > We run two sysplexes of about 12 LPARs each (NonProd vs Prod). Both plexes > have a single mcat shared across the plex (but not between plexes). We've > upgraded these from release to release over the last 10 years and never had > to use a second master catalog. In fact, I just checked our NonProd mcat > and it was created on 2007.005. > We use a single SYSRES with its own catalog, which resides on the SYSRES. > The SYSRES is swapped every month for a new one, which is how we introduce > maintenance, or even upgrades. > > I've seen no down sides to a single mcat for our setup, but as others have > noted, it will depend on the role of each system in the plex. For our setup > all LPARs serve the same purpose, just for different application instances. > > Bart > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Allan Staller > Sent: Tuesday, November 22, 2016 8:59 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > " Prior to this job I worked at a shop where we supported sysplexes from a > single system to up to 10 LPARs in a single sysplex. The master catalogs > were not shared , I think I would put forth one big reason for not sharing > the master catalog, would be system upgrades, when we went through the z/OS > upgrades, there were times where SYS1. Level data sets location changed > from one release to the next and the catalog needed to point to the new > location for the new release. We would upgrade one LPAR at a time in a > sysplex, which was once a week, so it would be several weeks to complete a > sysplex." > > This is a non-starter. As far as I am concerned, everything that can be > shared should be shared (Two of anything that do not agree worse than > nothing). If you go with separate MCATS, you must spend a great deal of > time ensuring they are in sync w/each other. > > Sure, you need multiple MCATs during the upgrade cycle, but when all is > done, there should be only one MCAT > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Nims,Alva John (Al) > Sent: Monday, November 21, 2016 3:44 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > We currently have a 2 LPAR sysplex and the master catalog in not shared. > Prior to this job I worked at a shop where we supported sysplexes from a > single system to up to 10 LPARs in a single sysplex. The master catalogs > were not shared , I think I would put forth one big reason for not sharing > the master catalog, would be system upgrades, when we went through the z/OS > upgrades, there were times where SYS1. Level data sets location changed > from one release to the next and the catalog needed to point to the new > location for the new release. We would upgrade one LPAR at a time in a > sysplex, which was once a week, so it would be several weeks to complete a > sysplex. > > I think there are a lot of questions you have to ask yourself about how > you are going to handle the sysplex and what you are going to keep in the > master catalog, besides SYS1. Note: I believe System Symbols are your > friend when setting up the catalog, for both data set names and VOLSER. > > > Al Nims > Systems Admin/Programmer 3 > UFIT > University of Florida > (352) 273-1298 > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Travis > Sent: Monday, November 21, 2016 3:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Catalogs in a SYSPLEX > > We are creating a SYSPLEX of two systems and there seems to be some debate > about using a single shared master catalog or multiple master catalogs on > each system. The IBM manuals recomme
Re: Catalogs in a SYSPLEX
I'd still like to know how this works. What's in your master cat? What's in your sysres cat? Ken On Tue, Nov 22, 2016 at 11:28 AM, van der Grijn, Bart (B) < bvandergr...@dow.com> wrote: > We run two sysplexes of about 12 LPARs each (NonProd vs Prod). Both plexes > have a single mcat shared across the plex (but not between plexes). We've > upgraded these from release to release over the last 10 years and never had > to use a second master catalog. In fact, I just checked our NonProd mcat > and it was created on 2007.005. > We use a single SYSRES with its own catalog, which resides on the SYSRES. > The SYSRES is swapped every month for a new one, which is how we introduce > maintenance, or even upgrades. > > I've seen no down sides to a single mcat for our setup, but as others have > noted, it will depend on the role of each system in the plex. For our setup > all LPARs serve the same purpose, just for different application instances. > > Bart > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Allan Staller > Sent: Tuesday, November 22, 2016 8:59 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > " Prior to this job I worked at a shop where we supported sysplexes from a > single system to up to 10 LPARs in a single sysplex. The master catalogs > were not shared , I think I would put forth one big reason for not sharing > the master catalog, would be system upgrades, when we went through the z/OS > upgrades, there were times where SYS1. Level data sets location changed > from one release to the next and the catalog needed to point to the new > location for the new release. We would upgrade one LPAR at a time in a > sysplex, which was once a week, so it would be several weeks to complete a > sysplex." > > This is a non-starter. As far as I am concerned, everything that can be > shared should be shared (Two of anything that do not agree worse than > nothing). If you go with separate MCATS, you must spend a great deal of > time ensuring they are in sync w/each other. > > Sure, you need multiple MCATs during the upgrade cycle, but when all is > done, there should be only one MCAT > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Nims,Alva John (Al) > Sent: Monday, November 21, 2016 3:44 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > We currently have a 2 LPAR sysplex and the master catalog in not shared. > Prior to this job I worked at a shop where we supported sysplexes from a > single system to up to 10 LPARs in a single sysplex. The master catalogs > were not shared , I think I would put forth one big reason for not sharing > the master catalog, would be system upgrades, when we went through the z/OS > upgrades, there were times where SYS1. Level data sets location changed > from one release to the next and the catalog needed to point to the new > location for the new release. We would upgrade one LPAR at a time in a > sysplex, which was once a week, so it would be several weeks to complete a > sysplex. > > I think there are a lot of questions you have to ask yourself about how > you are going to handle the sysplex and what you are going to keep in the > master catalog, besides SYS1. Note: I believe System Symbols are your > friend when setting up the catalog, for both data set names and VOLSER. > > > Al Nims > Systems Admin/Programmer 3 > UFIT > University of Florida > (352) 273-1298 > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Travis > Sent: Monday, November 21, 2016 3:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Catalogs in a SYSPLEX > > We are creating a SYSPLEX of two systems and there seems to be some debate > about using a single shared master catalog or multiple master catalogs on > each system. The IBM manuals recommend a single shared master catalog but > our CE has been advocating multiple catalogs. What are the pros and cons of > running each? We have two identical systems in the PLEX and for right now > there is no plan to add more, however that could change at any time in the > near future. > > > -- > 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: Catalogs in a SYSPLEX
> On Nov 29, 2016, at 1:43 PM, Jesse 1 Robinson <jesse1.robin...@sce.com> wrote: > > Brings to mind a near catastrophe in a previous shop where SYS1.PARMLIB was > kept on sysres. 'For compatibility' of course. Our VTAM guy made a change on > one system single-box that involved APF list. Shortly thereafter we switched > sysres for maintenance. The load library change was off of sysres, so it > remained, but the APF list change got replaced with the copy on the > already-copied new sysres. After IPL, VTAM would not come up. Logon > impossible. Remote data center in the Bay Area; we were in LA. We were about > to jump in a car and make the trip north when we figured out a fix, which > involved running a job that an operator *literally* punched onto cards. Many years ago I went through the same thing. Sysprog screwup he got fired. Ed > > Self-inflicted wound. Survived through a mechanism that has long ceased to > exist. No one needs that level of anxiety. > > . > . > 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 John Eells > Sent: Tuesday, November 29, 2016 9:33 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Catalogs in a SYSPLEX > > Jesse 1 Robinson wrote: >> I have to admit that locating MCAT on sysres avoids one step that we need to >> take. We run seven 'sysplexes' (some monoplex) that do not share any >> resources including MCAT. When we install a new release, there are often new >> sysres data sets that need to be cataloged on any plex by the time the new >> release gets migrated there. We have a Rexx that ferrets out any new data >> sets in the SMP/E 'master catalog' and creates a batch job with DEF NVSAM >> commands. That job gets sent to all sysplexes as soon as SMP/E install is >> complete. New catalog entries cause no problem. Old catalog entries that >> really ought to be deleted don't cause problems either except for OCD types. > > Of course, it introduces other steps, such as IMPORTing the usercats for each > plex, and either freezing or keeping current and master-catalogs-to-be in > sync. > > > -- > John Eells > IBM Poughkeepsie > ee...@us.ibm.com > > > -- > 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: Catalogs in a SYSPLEX
Brings to mind a near catastrophe in a previous shop where SYS1.PARMLIB was kept on sysres. 'For compatibility' of course. Our VTAM guy made a change on one system single-box that involved APF list. Shortly thereafter we switched sysres for maintenance. The load library change was off of sysres, so it remained, but the APF list change got replaced with the copy on the already-copied new sysres. After IPL, VTAM would not come up. Logon impossible. Remote data center in the Bay Area; we were in LA. We were about to jump in a car and make the trip north when we figured out a fix, which involved running a job that an operator *literally* punched onto cards. Self-inflicted wound. Survived through a mechanism that has long ceased to exist. No one needs that level of anxiety. . . 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 John Eells Sent: Tuesday, November 29, 2016 9:33 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Catalogs in a SYSPLEX Jesse 1 Robinson wrote: > I have to admit that locating MCAT on sysres avoids one step that we need to > take. We run seven 'sysplexes' (some monoplex) that do not share any > resources including MCAT. When we install a new release, there are often new > sysres data sets that need to be cataloged on any plex by the time the new > release gets migrated there. We have a Rexx that ferrets out any new data > sets in the SMP/E 'master catalog' and creates a batch job with DEF NVSAM > commands. That job gets sent to all sysplexes as soon as SMP/E install is > complete. New catalog entries cause no problem. Old catalog entries that > really ought to be deleted don't cause problems either except for OCD types. Of course, it introduces other steps, such as IMPORTing the usercats for each plex, and either freezing or keeping current and master-catalogs-to-be in sync. -- John Eells IBM Poughkeepsie ee...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
Jesse 1 Robinson wrote: >The rule for IT is much like the rule for life: as soon as you delete/discard >something, you will need it the next day. ;-) Next day? Aw, come on! In IT it is wayayayayayaya too long in the future. I rather expect that need within 15 minutes ... ;-) ... or while you're zzz and having a phone call interrupting your nightmare about your cruel heartless mother-in-law ... ;-) Even in RACF or STG admin work, if I do x, some y person is certainly complaining about z... Oh well... ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
Jesse 1 Robinson wrote: I have to admit that locating MCAT on sysres avoids one step that we need to take. We run seven 'sysplexes' (some monoplex) that do not share any resources including MCAT. When we install a new release, there are often new sysres data sets that need to be cataloged on any plex by the time the new release gets migrated there. We have a Rexx that ferrets out any new data sets in the SMP/E 'master catalog' and creates a batch job with DEF NVSAM commands. That job gets sent to all sysplexes as soon as SMP/E install is complete. New catalog entries cause no problem. Old catalog entries that really ought to be deleted don't cause problems either except for OCD types. Of course, it introduces other steps, such as IMPORTing the usercats for each plex, and either freezing or keeping current and master-catalogs-to-be in sync. -- John Eells IBM Poughkeepsie ee...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
I have to admit that locating MCAT on sysres avoids one step that we need to take. We run seven 'sysplexes' (some monoplex) that do not share any resources including MCAT. When we install a new release, there are often new sysres data sets that need to be cataloged on any plex by the time the new release gets migrated there. We have a Rexx that ferrets out any new data sets in the SMP/E 'master catalog' and creates a batch job with DEF NVSAM commands. That job gets sent to all sysplexes as soon as SMP/E install is complete. New catalog entries cause no problem. Old catalog entries that really ought to be deleted don't cause problems either except for OCD types. The rule for IT is much like the rule for life: as soon as you delete/discard something, you will need it the next day. ;-) . . 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 Jousma, David Sent: Tuesday, November 29, 2016 6:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Catalogs in a SYSPLEX Agreed, way too much risk. We don’t swap master cat's at all either. No reason to, except maybe those shops that cannot fit the entire SYSRES on one volume, so you have the issue where DSN A is cataloged on the first volume of the set pre-upgrade, and post-upgrade it got placed on a different volume. We solved that years ago by using mod-27's as sysres, and now mod-54's. _ Dave Jousma Manager 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 [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Monday, November 28, 2016 4:57 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX As noted earlier in this thread, sysres datasets should be cataloged with volser ** and unit . That tells the system to look on the currently IPLed sysres regardless of volume name. BTW I don't subscribe to the floating MCAT strategy. Our master catalog lives away from sysres and therefore does not change on sysres swap. We've done this forever and don't see any serious problems. And you don't need multiple MCATs during upgrades as long you always call LINKLIB 'SYS1.LINKLIB' -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
Agreed, way too much risk. We don’t swap master cat's at all either. No reason to, except maybe those shops that cannot fit the entire SYSRES on one volume, so you have the issue where DSN A is cataloged on the first volume of the set pre-upgrade, and post-upgrade it got placed on a different volume. We solved that years ago by using mod-27's as sysres, and now mod-54's. _ Dave Jousma Manager 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 [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Monday, November 28, 2016 4:57 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX As noted earlier in this thread, sysres datasets should be cataloged with volser ** and unit . That tells the system to look on the currently IPLed sysres regardless of volume name. BTW I don't subscribe to the floating MCAT strategy. Our master catalog lives away from sysres and therefore does not change on sysres swap. We've done this forever and don't see any serious problems. And you don't need multiple MCATs during upgrades as long you always call LINKLIB 'SYS1.LINKLIB'. . . 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 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: Catalogs in a SYSPLEX
Jesse 1 Robinson wrote: As noted earlier in this thread, sysres datasets should be cataloged with volser ** and unit . That tells the system to look on the currently IPLed sysres regardless of volume name. BTW I don't subscribe to the floating MCAT strategy. Our master catalog lives away from sysres and therefore does not change on sysres swap. We've done this forever and don't see any serious problems. And you don't need multiple MCATs during upgrades as long you always call LINKLIB 'SYS1.LINKLIB'. I prefer Skip's approach, for what it's worth. In my view, the master catalog can be fully divorced from the software, as is the case for other operational data sets, and should be. Minor work is needed once in a while for things you have to add when we add data sets to z/OS and minor cleanup is needed once in a while for data sets we delete from z/OS and you're past the point where you will back out to the old release, but if you keep the same data set names and relative volume locations this cleanup is generally less work and holds fewer opportunities for error than creating new master catalogs or cloning existing master catalogs. The more operational data sets you can leave as-is during migrations, the faster your migrations are likely to be. I'll note that shared master catalogs have an upside and a downside. The upside is that the frequency of failure is lower because one volume will fail less often than any one of *n* volumes. (This is not quite 1/*n* but it's close enough to that for government work.) The downside is that the impact of failures or egregious human error is greater, affecting *n* systems rather than one. Some thought should be given to sharing boundaries. For instance, you might avoid sharing between systems that back each other up if you can locate them in different storage subsystems. Sharing them is not hard given workable naming conventions for system-specific data sets, such as but of course not limited to page data sets. Also, a reasonable alternative to ** in indirect catalog entries is using the system-defined symbol From a readability standpoint I prefer the latter although they are functionally equivalent. Also, for anyone still using more than one target volume, you can base symbols for volumes other than IPL volumes from using a naming convention to derive the rest; indirect cataloging works even for multiple volumes using such derived system symbols. -- John Eells IBM Poughkeepsie ee...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
As noted earlier in this thread, sysres datasets should be cataloged with volser ** and unit . That tells the system to look on the currently IPLed sysres regardless of volume name. BTW I don't subscribe to the floating MCAT strategy. Our master catalog lives away from sysres and therefore does not change on sysres swap. We've done this forever and don't see any serious problems. And you don't need multiple MCATs during upgrades as long you always call LINKLIB 'SYS1.LINKLIB'. . . 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 Ken Smith Sent: Monday, November 28, 2016 12:49 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Catalogs in a SYSPLEX I like this approach! But I thought certain data sets used in NIP and early phases of IPL had to be in the master cat, e.g., SYS1.LPALIB which presumably is in your SYSRES cat? How does it work? Ken On Tue, Nov 22, 2016 at 11:28 AM, van der Grijn, Bart (B) < bvandergr...@dow.com> wrote: > We run two sysplexes of about 12 LPARs each (NonProd vs Prod). Both > plexes have a single mcat shared across the plex (but not between > plexes). We've upgraded these from release to release over the last 10 > years and never had to use a second master catalog. In fact, I just > checked our NonProd mcat and it was created on 2007.005. > We use a single SYSRES with its own catalog, which resides on the SYSRES. > The SYSRES is swapped every month for a new one, which is how we > introduce maintenance, or even upgrades. > > I've seen no down sides to a single mcat for our setup, but as others > have noted, it will depend on the role of each system in the plex. For > our setup all LPARs serve the same purpose, just for different application > instances. > > Bart > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Allan Staller > Sent: Tuesday, November 22, 2016 8:59 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > " Prior to this job I worked at a shop where we supported sysplexes > from a single system to up to 10 LPARs in a single sysplex. The > master catalogs were not shared , I think I would put forth one big > reason for not sharing the master catalog, would be system upgrades, > when we went through the z/OS upgrades, there were times where SYS1. > Level data sets location changed from one release to the next and the > catalog needed to point to the new location for the new release. We > would upgrade one LPAR at a time in a sysplex, which was once a week, > so it would be several weeks to complete a sysplex." > > This is a non-starter. As far as I am concerned, everything that can > be shared should be shared (Two of anything that do not agree worse > than nothing). If you go with separate MCATS, you must spend a great > deal of time ensuring they are in sync w/each other. > > Sure, you need multiple MCATs during the upgrade cycle, but when all > is done, there should be only one MCAT > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Nims,Alva John (Al) > Sent: Monday, November 21, 2016 3:44 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > We currently have a 2 LPAR sysplex and the master catalog in not shared. > Prior to this job I worked at a shop where we supported sysplexes from > a single system to up to 10 LPARs in a single sysplex. The master > catalogs were not shared , I think I would put forth one big reason > for not sharing the master catalog, would be system upgrades, when we > went through the z/OS upgrades, there were times where SYS1. Level > data sets location changed from one release to the next and the > catalog needed to point to the new location for the new release. We > would upgrade one LPAR at a time in a sysplex, which was once a week, > so it would be several weeks to complete a sysplex. > > I think there are a lot of questions you have to ask yourself about > how you are going to handle the sysplex and what you are going to keep > in the master catalog, besides SYS1. Note: I believe System Symbols > are your friend when setting up the catalog, for both data set names and > VOLSER. > > > Al Nims > Systems Admin/Programmer 3 > UFIT > University of Florida > (352) 273-1298 > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Travis > Sent: Monday, November 21, 201
Re: Catalogs in a SYSPLEX
I like this approach! But I thought certain data sets used in NIP and early phases of IPL had to be in the master cat, e.g., SYS1.LPALIB which presumably is in your SYSRES cat? How does it work? Ken On Tue, Nov 22, 2016 at 11:28 AM, van der Grijn, Bart (B) < bvandergr...@dow.com> wrote: > We run two sysplexes of about 12 LPARs each (NonProd vs Prod). Both plexes > have a single mcat shared across the plex (but not between plexes). We've > upgraded these from release to release over the last 10 years and never had > to use a second master catalog. In fact, I just checked our NonProd mcat > and it was created on 2007.005. > We use a single SYSRES with its own catalog, which resides on the SYSRES. > The SYSRES is swapped every month for a new one, which is how we introduce > maintenance, or even upgrades. > > I've seen no down sides to a single mcat for our setup, but as others have > noted, it will depend on the role of each system in the plex. For our setup > all LPARs serve the same purpose, just for different application instances. > > Bart > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Allan Staller > Sent: Tuesday, November 22, 2016 8:59 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > " Prior to this job I worked at a shop where we supported sysplexes from a > single system to up to 10 LPARs in a single sysplex. The master catalogs > were not shared , I think I would put forth one big reason for not sharing > the master catalog, would be system upgrades, when we went through the z/OS > upgrades, there were times where SYS1. Level data sets location changed > from one release to the next and the catalog needed to point to the new > location for the new release. We would upgrade one LPAR at a time in a > sysplex, which was once a week, so it would be several weeks to complete a > sysplex." > > This is a non-starter. As far as I am concerned, everything that can be > shared should be shared (Two of anything that do not agree worse than > nothing). If you go with separate MCATS, you must spend a great deal of > time ensuring they are in sync w/each other. > > Sure, you need multiple MCATs during the upgrade cycle, but when all is > done, there should be only one MCAT > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Nims,Alva John (Al) > Sent: Monday, November 21, 2016 3:44 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > We currently have a 2 LPAR sysplex and the master catalog in not shared. > Prior to this job I worked at a shop where we supported sysplexes from a > single system to up to 10 LPARs in a single sysplex. The master catalogs > were not shared , I think I would put forth one big reason for not sharing > the master catalog, would be system upgrades, when we went through the z/OS > upgrades, there were times where SYS1. Level data sets location changed > from one release to the next and the catalog needed to point to the new > location for the new release. We would upgrade one LPAR at a time in a > sysplex, which was once a week, so it would be several weeks to complete a > sysplex. > > I think there are a lot of questions you have to ask yourself about how > you are going to handle the sysplex and what you are going to keep in the > master catalog, besides SYS1. Note: I believe System Symbols are your > friend when setting up the catalog, for both data set names and VOLSER. > > > Al Nims > Systems Admin/Programmer 3 > UFIT > University of Florida > (352) 273-1298 > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Travis > Sent: Monday, November 21, 2016 3:54 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Catalogs in a SYSPLEX > > We are creating a SYSPLEX of two systems and there seems to be some debate > about using a single shared master catalog or multiple master catalogs on > each system. The IBM manuals recommend a single shared master catalog but > our CE has been advocating multiple catalogs. What are the pros and cons of > running each? We have two identical systems in the PLEX and for right now > there is no plan to add more, however that could change at any time in the > near future. > > > -- > 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: Catalogs in a SYSPLEX
We run two sysplexes of about 12 LPARs each (NonProd vs Prod). Both plexes have a single mcat shared across the plex (but not between plexes). We've upgraded these from release to release over the last 10 years and never had to use a second master catalog. In fact, I just checked our NonProd mcat and it was created on 2007.005. We use a single SYSRES with its own catalog, which resides on the SYSRES. The SYSRES is swapped every month for a new one, which is how we introduce maintenance, or even upgrades. I've seen no down sides to a single mcat for our setup, but as others have noted, it will depend on the role of each system in the plex. For our setup all LPARs serve the same purpose, just for different application instances. Bart -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Tuesday, November 22, 2016 8:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX " Prior to this job I worked at a shop where we supported sysplexes from a single system to up to 10 LPARs in a single sysplex. The master catalogs were not shared , I think I would put forth one big reason for not sharing the master catalog, would be system upgrades, when we went through the z/OS upgrades, there were times where SYS1. Level data sets location changed from one release to the next and the catalog needed to point to the new location for the new release. We would upgrade one LPAR at a time in a sysplex, which was once a week, so it would be several weeks to complete a sysplex." This is a non-starter. As far as I am concerned, everything that can be shared should be shared (Two of anything that do not agree worse than nothing). If you go with separate MCATS, you must spend a great deal of time ensuring they are in sync w/each other. Sure, you need multiple MCATs during the upgrade cycle, but when all is done, there should be only one MCAT -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Nims,Alva John (Al) Sent: Monday, November 21, 2016 3:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX We currently have a 2 LPAR sysplex and the master catalog in not shared. Prior to this job I worked at a shop where we supported sysplexes from a single system to up to 10 LPARs in a single sysplex. The master catalogs were not shared , I think I would put forth one big reason for not sharing the master catalog, would be system upgrades, when we went through the z/OS upgrades, there were times where SYS1. Level data sets location changed from one release to the next and the catalog needed to point to the new location for the new release. We would upgrade one LPAR at a time in a sysplex, which was once a week, so it would be several weeks to complete a sysplex. I think there are a lot of questions you have to ask yourself about how you are going to handle the sysplex and what you are going to keep in the master catalog, besides SYS1. Note: I believe System Symbols are your friend when setting up the catalog, for both data set names and VOLSER. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Travis Sent: Monday, November 21, 2016 3:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalogs in a SYSPLEX We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared master catalog or multiple master catalogs on each system. The IBM manuals recommend a single shared master catalog but our CE has been advocating multiple catalogs. What are the pros and cons of running each? We have two identical systems in the PLEX and for right now there is no plan to add more, however that could change at any time in the near future. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
" Prior to this job I worked at a shop where we supported sysplexes from a single system to up to 10 LPARs in a single sysplex. The master catalogs were not shared , I think I would put forth one big reason for not sharing the master catalog, would be system upgrades, when we went through the z/OS upgrades, there were times where SYS1. Level data sets location changed from one release to the next and the catalog needed to point to the new location for the new release. We would upgrade one LPAR at a time in a sysplex, which was once a week, so it would be several weeks to complete a sysplex." This is a non-starter. As far as I am concerned, everything that can be shared should be shared (Two of anything that do not agree worse than nothing). If you go with separate MCATS, you must spend a great deal of time ensuring they are in sync w/each other. Sure, you need multiple MCATs during the upgrade cycle, but when all is done, there should be only one MCAT -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Nims,Alva John (Al) Sent: Monday, November 21, 2016 3:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX We currently have a 2 LPAR sysplex and the master catalog in not shared. Prior to this job I worked at a shop where we supported sysplexes from a single system to up to 10 LPARs in a single sysplex. The master catalogs were not shared , I think I would put forth one big reason for not sharing the master catalog, would be system upgrades, when we went through the z/OS upgrades, there were times where SYS1. Level data sets location changed from one release to the next and the catalog needed to point to the new location for the new release. We would upgrade one LPAR at a time in a sysplex, which was once a week, so it would be several weeks to complete a sysplex. I think there are a lot of questions you have to ask yourself about how you are going to handle the sysplex and what you are going to keep in the master catalog, besides SYS1. Note: I believe System Symbols are your friend when setting up the catalog, for both data set names and VOLSER. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Travis Sent: Monday, November 21, 2016 3:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalogs in a SYSPLEX We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared master catalog or multiple master catalogs on each system. The IBM manuals recommend a single shared master catalog but our CE has been advocating multiple catalogs. What are the pros and cons of running each? We have two identical systems in the PLEX and for right now there is no plan to add more, however that could change at any time in the near future. -- 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 ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
On Mon, 21 Nov 2016 21:44:19 +, Nims,Alva John (Al) wrote: >I would put forth one big reason for not sharing the master catalog, >would be system upgrades, when we went through the z/OS upgrades, >there were times where SYS1. Level data sets location changed from >one release to the next and the catalog needed to point to the new >location for the new release. You can use system symbols for this. Define a symbol to represent the volser of every data set that was on volume X that is now on volume Y. Recatalog those data sets using the new symbol. When you IPL the new system, you will define the symbol to have a value of Y. When all the systems have been upgraded and you won't be going back, recatalog those data sets normally. Is it a better solution? YMMV. It worked for me way back in the days when we had multi-volume SYSRES sets and had to move things. Is anyone still using multi-volume sysres? >System Symbols are your friend when setting up the catalog, for both >data set names and VOLSER. Yes, they are. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EXTERNAL: Re: Catalogs in a SYSPLEX
All of my Sysplexes each have a shared single MCAT per plex. Setting up a Sysplex is probably where the recommendation to a single MCAT is located. In an emergency the LOADxx can be edited to point to any other MCAT and they will all serve to get a system up and running. Additionally in each physical Data Center we have a 3 pack Rescue system (built from Mark Zeldens sources - Thanks Mark !) that normally lives somewhat back level to ensure new maintenance etc. doesn't also render the system unusable. I wouldn't try to run a complex Sysplex with multiple Master Cats. 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 Travis Sent: Monday, November 21, 2016 2:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL: Re: Catalogs in a SYSPLEX I was doing some research and I cannot seem to find any specific mention of using a single shared master catalog in the manuals. It doesn't mean I was looking in the correct manuals it just means that what I had been told may not be 100% accurate. The manuls do seem to IMPLY that a shared master catalog is the way to go but there is nothing recommending one over the other that I can see. -- 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
Re: Catalogs in a SYSPLEX
So what is the intent of your configuration? To take advantage of all the wonderfulness that is SYSPLEX :) Separate but equal? Or are they running from a common SYSRES Set? Other??? We will have 2 systems that are identical. They are going to have a common SYSRES with a secondary SYSRES to swap to for maintenance and upgrades. They also will share DASD so whatever data sets are on those DASD are accessible by both systems. Hence the catalog question. Right now we have 3 LPAR's (Production, Test and Maintenance). We have DASD accessible to all three with data sets on them. In order for those data sets to be viewed on other LPAR's than the LPAR we create them on we must catalog them on each system. I would imagine that this is analogous to the processes involved with multiple master catalogs or shared master catalogs in a sysplex. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
You can do either and will some associated issues. Here are some: If you have a MCAT for each LPAR you will have so many MCAT's + its backup to maintain and garbage in it piles up with time. If you have a shared MCAT, you need to maintain one MCAT/SYSPLEX and one backup.At the time of z/OS upgrade create a new SYSPLEX MCAT (you may have one character in MCAT specific to z/OS versrion/release in MCAT name) ( gives you opportunity to cleanup / gives you opportunity to test z/OS upgrade in DR ahead of time). One will need to keep two MCAT SYNCed up during the upgrade. Regards, Rajesh -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Travis Sent: Monday, November 21, 2016 4:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX I was doing some research and I cannot seem to find any specific mention of using a single shared master catalog in the manuals. It doesn't mean I was looking in the correct manuals it just means that what I had been told may not be 100% accurate. The manuls do seem to IMPLY that a shared master catalog is the way to go but there is nothing recommending one over the other that I can see. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
By using INDIRECT CATALOG you can use different SYSRES Sets, but the same SYS1.** names. Lizette -Original Message- >From: Lizette Koehler <stars...@mindspring.com> >Sent: Nov 21, 2016 3:10 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: Catalogs in a SYSPLEX > >So the answers are > > It depends on what you want to do > Your milage May Vary (YMMV) > >If you want to access the datasets from either Plex easily, a Shared Master is >okay. Remember the master cat should only have Aliases to usercats, and SYS1 >datasets for that environment. If you want SYS1.LINKLIB that is different >from both Plexes, then you probably want separate MCats. > >If both plexes can "share" the common datasets, then you can get by with one >MCAT. > >Or the Mcat on PLEX has the Mcat on Plex b as a user cat and vise versa. > > >So what is the intent of your configuration? > >Separate but equal? Or are they running from a common SYSRES Set? Other??? > > >Lizette > > >-Original Message- >>From: Travis <tbr...@aessuccess.org> >>Sent: Nov 21, 2016 1:53 PM >>To: IBM-MAIN@LISTSERV.UA.EDU >>Subject: Catalogs in a SYSPLEX >> >>We are creating a SYSPLEX of two systems and there seems to be some debate >>about using a single shared master catalog or multiple master catalogs on >>each system. The IBM manuals recommend a single shared master catalog but our >>CE has been advocating multiple catalogs. What are the pros and cons of >>running each? We have two identical systems in the PLEX and for right now >>there is no plan to add more, however that could change at any time in the >>near future. >> > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
Biggest problem I see with multiple master catalogs is that you have to keep entries in synch. First time you debug a weird problem resulting from out-of-synch catalogs, I think you'll want a single one. As for installing software maintenance, you should alternate between (at least) two sysres volumes. Swap from one to the other to migrate software upgrade. In case of problems, fall back to the older level. Sysres data sets are cataloged like this: VOLSER** DEVTYPE--X'' This will resolve to the volume you IPLed from on each system. . . 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 Travis Sent: Monday, November 21, 2016 1:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Catalogs in a SYSPLEX I was doing some research and I cannot seem to find any specific mention of using a single shared master catalog in the manuals. It doesn't mean I was looking in the correct manuals it just means that what I had been told may not be 100% accurate. The manuls do seem to IMPLY that a shared master catalog is the way to go but there is nothing recommending one over the other that I can see. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
So the answers are It depends on what you want to do Your milage May Vary (YMMV) If you want to access the datasets from either Plex easily, a Shared Master is okay. Remember the master cat should only have Aliases to usercats, and SYS1 datasets for that environment. If you want SYS1.LINKLIB that is different from both Plexes, then you probably want separate MCats. If both plexes can "share" the common datasets, then you can get by with one MCAT. Or the Mcat on PLEX has the Mcat on Plex b as a user cat and vise versa. So what is the intent of your configuration? Separate but equal? Or are they running from a common SYSRES Set? Other??? Lizette -Original Message- >From: Travis <tbr...@aessuccess.org> >Sent: Nov 21, 2016 1:53 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Catalogs in a SYSPLEX > >We are creating a SYSPLEX of two systems and there seems to be some debate >about using a single shared master catalog or multiple master catalogs on each >system. The IBM manuals recommend a single shared master catalog but our CE >has been advocating multiple catalogs. What are the pros and cons of running >each? We have two identical systems in the PLEX and for right now there is no >plan to add more, however that could change at any time in the near future. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
I was doing some research and I cannot seem to find any specific mention of using a single shared master catalog in the manuals. It doesn't mean I was looking in the correct manuals it just means that what I had been told may not be 100% accurate. The manuls do seem to IMPLY that a shared master catalog is the way to go but there is nothing recommending one over the other that I can see. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
We currently have a 2 LPAR sysplex and the master catalog in not shared. Prior to this job I worked at a shop where we supported sysplexes from a single system to up to 10 LPARs in a single sysplex. The master catalogs were not shared , I think I would put forth one big reason for not sharing the master catalog, would be system upgrades, when we went through the z/OS upgrades, there were times where SYS1. Level data sets location changed from one release to the next and the catalog needed to point to the new location for the new release. We would upgrade one LPAR at a time in a sysplex, which was once a week, so it would be several weeks to complete a sysplex. I think there are a lot of questions you have to ask yourself about how you are going to handle the sysplex and what you are going to keep in the master catalog, besides SYS1. Note: I believe System Symbols are your friend when setting up the catalog, for both data set names and VOLSER. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Travis Sent: Monday, November 21, 2016 3:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalogs in a SYSPLEX We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared master catalog or multiple master catalogs on each system. The IBM manuals recommend a single shared master catalog but our CE has been advocating multiple catalogs. What are the pros and cons of running each? We have two identical systems in the PLEX and for right now there is no plan to add more, however that could change at any time in the near future. -- 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: Catalogs in a SYSPLEX
A lot depends on whether you're creating a net new member or combining two existing systems into a single plex. As I said in a previous thread, combining systems is very tough unless you're willing to put up with the vagaries of a 'bronze-plex'. If you're creating a new system, you can clone the existing one. You should aim to share everything that can be shared. I don't know why anyone would stop short of total sharing: one master catalog; one RACF (or other security product) data base; one JES spool. If someone can give you a compelling reason for separate anything--like page data sets--then you could consider it. I would be very dubious about proposed subdivisions. . . 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 Travis Sent: Monday, November 21, 2016 12:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Catalogs in a SYSPLEX We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared master catalog or multiple master catalogs on each system. The IBM manuals recommend a single shared master catalog but our CE has been advocating multiple catalogs. What are the pros and cons of running each? We have two identical systems in the PLEX and for right now there is no plan to add more, however that could change at any time in the near future. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Catalogs in a SYSPLEX
At our shop we have three master catalogs in the same sysplex. We run three "levels" of lpars and the master catalogs are by level. Our three tech lpars share a master catalog. Our three application test lpars share a different master catalog. Our 6 production lpars share a different master catalog. So yes you can have more than one master catalog, it just depends on how things are laid out. We run with shared DASD across all the lpars. So depending on what we are doing we have to remember to update all three master catalogs or just update one master catalog. You have to be careful about any VSAM dataset that might be in your master catalog(s). You don't want a VSAM dataset in two master catalogs. We have the master catalogs on their own (different) volumes. You don't want more than one master catalog on a volume. Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Travis Sent: Monday, November 21, 2016 14:54 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Catalogs in a SYSPLEX We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared master catalog or multiple master catalogs on each system. The IBM manuals recommend a single shared master catalog but our CE has been advocating multiple catalogs. What are the pros and cons of running each? We have two identical systems in the PLEX and for right now there is no plan to add more, however that could change at any time in the near future. -- 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
Catalogs in a SYSPLEX
We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared master catalog or multiple master catalogs on each system. The IBM manuals recommend a single shared master catalog but our CE has been advocating multiple catalogs. What are the pros and cons of running each? We have two identical systems in the PLEX and for right now there is no plan to add more, however that could change at any time in the near future. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
