I know of one very large customer with many hundred of LPARs, changed they way they did maintenance. If they had MVSA, MVSB,MCSC,MVSD, they created a new LPAR MVSE, with all the maintenance of all products on it. They added it to the sysplex, and when it proved to work, they removed(killed) MVSA. Create a new LPAR MVSA and add it in - and remove MVSB. Within a few weeks they had all LPARs up and running at the latest level, and did one IPL a quarter. This saved them a lot of complexity as all products were refreshed at the same time (to the IBM CST level). Colin
On Tue, 18 Jul 2023 at 11:53, David Spiegel < 00000468385049d1-dmarc-requ...@listserv.ua.edu> wrote: > Hi Brian, > One of my customers decided (many years ago) to upgrade software/apply > maintenance once a year (on each of their 4 complexes). > There are not enough weekends in the year to do this more frequently > (due to other groups doing upgrades and "blocked out" weekends). > > Regards, > David > > On 2023-07-18 02:16, Brian Westerman wrote: > > All RSU's are not created equal. The quarterly ones (i.e. 2303 2306 > 2309 2312), are tested by IBM differently and tend to be "easier" to > install. > > > > There is NEVER a good reason to skip maintenance for a long period of > time. Only doing maintenance when you install a new copy of the OS is a > pretty silly idea. You are placing yourself at the vagaries of IBM builds > and not any better off than updating with the RSU's. > > > > It sounds like someone is probably just being very lazy. I work with > literally over 300 sites, and I hear a lot of odd thinking on how > "everybody" does maintenance and installations, and for the most part it's > a lot like operating on yourself or making investing decisions because of > something you saw on tictoc or instagram. :) > > > > Maintenance isn't hard to put on, you just have to have a plan and > follow it. > > > > Brian > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN