You are 100% correct, there are about 50 datasets that I ALWAYS enlarge during the installation for just the reason you specified, IBM sizes them for delivery, not for applying maintenance later. Then there are the ones that ALWAYS need to be updated like HASPSPACE and the checkpoints, as well as the SMF datasets, the SMS datasets, parmlib, and most of the SMPE datasets. Going with IBM's default assignments would make later maintenance application certain to fail and you would need a lot of time to enlarge a lot of datasets that you could have handled during the initial installation in a few minutes.
My problem with the new installation method is that it "should" have been set up such that for all of 2.5 (and maybe 2.6) that you had the choice of Serverpac AND z/OSMF so that you could work out the issues. in this case, IBM is giving everyone a very small number of months to get things corrected, when it's likely that you won't even realize that something was messed up until you apply maintenance at some "later" time. I am unaware of any time in the past that IBM was so aggressive with something as completely untried. You could use z/OSMF with DB/2 etc, but for sites that don't have those products there is no way to "try it out". This is the first shot at the whole operating system, and there is very little parallel time being provided. That's never a good idea with something as large and complex as a complete z/OS installation. How can the company that makes sure that you can run code form 1960 in 2021 be some completely oblivious to providing any path "other" than complete installation method replacement? Brian On Tue, 20 Jul 2021 02:18:10 -0500, Barbara Nitz <[email protected]> wrote: >>You can't change the size of a dataset and you can't change PDS to PDSE. It's >>easy in ServerPac to mass change to PDSE. It skips ones that aren't eligible. > >You can't? As far as I am concerned that is a definite roadblock. IBM never >sizes the data sets in such a way that they won't go x37 at the first apply. I >routinely at least double allocations for things like linklib and miglib and >essentially all linklist datasets because they don't have extents and are more >prone to x37. > >It's a good thing we have always planned to order 2.5 as soon as it becomes >available, so I get to use serverpac for my last ever z/OS install. The one in >four years will have to be done by my successor because I'll be almost retired >by then. > >Never mind that we haven't set up z/OSMF, either. Once we migrate to the z15, >we can take advantage of system 'recovery' boost so z/OSMF can come up on the >teeny tiny sysprog lpars. > >Regards, Barbara > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
