Yes sure: Weights, Defined Capacities and Group Capacities. And all done automated by SA, after one push on the button: change LPAR controls, activate CBU, move workloads. LPAR memory etc. are sufficient to take the combined load, but we have defined reserved memory just in case.
Kees. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Martin Packer > Sent: 11 February, 2019 15:07 > To: [email protected] > Subject: Re: Wells Fargo? Well f*&%#d at the moment: Data center up in > smoke, bank website, app down . The Register > > Kees, I would hope that - as part of adding the capacity - you adjust > LPAR > definitions, especially weights. Even if that is a "null" adjustment. > > Cheers, Martin > > Martin Packer > > zChampion, Systems Investigator & Performance Troubleshooter, IBM > > +44-7802-245-584 > > email: [email protected] > > Twitter / Facebook IDs: MartinPacker > > Blog: > https://www.ibm.com/developerworks/mydeveloperworks/blogs/MartinPacker > > Podcast Series (With Marna Walle): https://developer.ibm.com/tv/mpt/ > or > > https://itunes.apple.com/gb/podcast/mainframe-performance- > topics/id1127943573?mt=2 > > > Youtube channel: > https://www.youtube.com/channel/UCu_65HaYgksbF6Q8SQ4oOvA > > > > From: "Vernooij, Kees (ITOP NM) - KLM" <[email protected]> > To: [email protected] > Date: 11/02/2019 13:59 > Subject: Re: Wells Fargo? Well f*&%#d at the moment: Data center > up > in smoke, bank website, app down . The Register > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > We run in 2 sites continuously. Mainly Prod in 1 site and Dev/Acc in the > other site, a CF in both sites and Dasd mirrored between the sites. > Our DRP consists of moving workload from 1 site's LPARs to the > corresponding LPARs in the other site and adding capacity b.m.o. CBUs. > No > manipulation of LPARs. > We do this from time to time, sometimes as part of a DRP test, recently > also because of a potentially disastrous power maintenance in a site. > A piece of cake, compared to the comments I read above. > > Kees. > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > On > > Behalf Of Allan Staller > > Sent: 11 February, 2019 14:30 > > To: [email protected] > > Subject: Re: Wells Fargo? Well f*&%#d at the moment: Data center up in > > smoke, bank website, app down . The Register > > > > I have heard of a company in the Far East the periodically (every 6 > > mths., IIRC) flips from site A to site B (and back). > > Aus(?) to Phillipines ?) and back. > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > Behalf > > Of Savor, Thomas (Alpharetta) > > Sent: Friday, February 8, 2019 7:08 PM > > To: [email protected] > > Subject: Re: Wells Fargo? Well f*&%#d at the moment: Data center up in > > smoke, bank website, app down . The Register > > > > >We've been doing DR mirroring for 20 years. It gets tested often. > We've > > moved production twice to another >data center using our procedures. > > What we've never done is run production in another location > > >temporarily. 'Temporary' means move it, run it until at least one > > transaction is committed, then move it >*all* back. That is hugely > > complex and costly. > > > > >A lot of management fantasizes about a big A-B switch that we throw > one > > way or the other. So wrong. > > > > About 5-6 years ago, I was working as a vendor (Daily Support) for > > Credit Card Software for Halifax/Bank of Scotland. I believe the > first > > time I was given a "heads up" was when we were supporting 12 Million > > Cardholders. The "Heads up" was that on Friday evening at 6pm Main > site > > was going to shut down and the whole weekend PRODUCTION was going to > run > > on DR site, then 6am Monday Morning, Main site is to come back up and > > continue as if nothing happened !!! I literally peed in my pants !!! > > Probably everyone in Atlanta could hear me...NOOOOOOOOO !!! Thinking > of > > all the network signons with Visa and Mastercard...all the credit card > > Authorizations...there was absolutely zero chance of this working > > without issues. > > > > Well, came in Monday morning after receiving no calls over the week- > end > > ....everything was fine. We ran the Batch Monday night...and that > would > > be pulling in transactions from over the week-end from DR site. > > NO ISSUES !!! Everything was fine. > > > > Whoever did this, from a Systems perspective....I tip my hat. I've > > never seen someone do this with Production, but it worked fine...so > what > > do I know. Never seen anyone else do this in my 42 years of > Mainframing > > either. > > > > Unfortunately, Halifax/Bank of Scotland is no longer with us. They > were > > absorbed by Lloyds Banking Group. > > > > > > Thanks, > > Tom Savor > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] 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 [email protected] with the message: INFO IBM-MAIN > ******************************************************** > For information, services and offers, please visit our web site: > https://urldefense.proofpoint.com/v2/url?u=http- > 3A__www.klm.com&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=BsPGKdq7-Vl8MW2- > WOWZjlZ0NwmcFSpQCLphNznBSDQ&m=ms- > 3LFKgtmju0Im4KkSzyo_8EyikKrekEEdXxBG46eI&s=83PafHr- > Ln69WcriMfeycT49MQPUjSsOyYIl27BcMfc&e= > . 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 [email protected] with the message: INFO IBM-MAIN > > > > > Unless stated otherwise above: > IBM United Kingdom Limited - Registered in England and Wales with number > 741598. > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 > 3AU > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] 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 [email protected] with the message: INFO IBM-MAIN
