On Sun, 3 Aug 2025 00:13:01 +1000, Clement Clarke wrote: > ... >"With SMS, the JCL becomes much cleaner. The system handles the allocation >details based on its policy. A ... > I see wishful thinking in "The system ... its policy." It's not the system but the data administrator who determines policies. And the end user or department is still burdened with choosing a class with suitable details. And the need for multiple classes for combinations of DCB attributes.
Pre-SMS, I worked with a site that required a paper request for any permanently cataloged data set. I have long wished for a UNIX-like disposition status meaning, "NEW if possible; otherwise overwrite it. I can simulate that wit an additional DD statement. And for exponentially increasing extent sizes, which might mitigate space lost by over-allocation. UNIX has per-user space quotas with a performance cost; MVS addressed the need by supporting a separate filesystem for each user, again with over-allocation penalty. How about a scheme where a job could wait until needed temporary space became available? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
