I see the requirements as being different for dlib, target and operational datasets. For operational datasets, there is simply no way to have a "one size fits all", so IBM should make it as easy to tailor those as in the older delivery vehicles.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Brian Westerman [brian_wester...@syzygyinc.com] Sent: Wednesday, July 21, 2021 1:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Serverpac installs January 2022 and beyond - Requests Making everything bigger is not a good option. Not everything "needs" to be bigger, but there are those that even 40% won't be enough. The Serverpac used to ship with SMF and JES spool/checkpoint and SMF on the catalog volume, and I'm sure no one probably leaves it there, but the size of the datasets is a big issue. For instance, if you wanted to use a full 3390-27 for the spool dataset (not an unreasonable size), how would you do that using z/OSMF? My assumption from your previous answers is that you can't. It's not hard to change this later, but you have just made the installation process a LOT more difficult for people. Some people will want a 3390-9 or a 3390-54, and that's just the one single dataset, there are lots more that will end up with exactly the same issue(s). I think creating z/OSMF product delivery without the ability to change the size and location of the datasets (easily) is a bad idea. Among all of the other "bad ideas" I have already identified in z/OSMF. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
