> On Sunday, July 30, 2023 at 08:23:54 PM PDT, Andrew Rowley > <and...@blackhillsoftware.com> wrote:
>> Whatever. We use automount, and the "space" wasted is way too trivial to >> worry about. > If it's trivial, you're probably not using actually using it. Unix people don't understand trivial for z/OS. z/OS files are littered with unused space in each block and at the end of the file. This can be very significant. In many cases, we consider a lot of wasted space trivial. There are a lot of things we consider trivial that is considered wasteful to Unix mentality (e.g. redundancy). A Unix file will never waste more than 4K. > A low end laptop has 250GB available. How much space should a z/OS user > be able to use (to do their job) before they have to make a special > request to the storage management group? 10GB? 100GB? Typical Unix mindset is "me" instead of "business needs". This same problem will exist in a properly configured Unix system that has set disk quotas. Just because most do not implement disk quotas doesn't make it right. It's absurd that on a multi-million $ computer, a user expects to allocate a 100GB file that is for their private use. It would be different if multiple users were accessing that file. This file would be far cheaper on a $5,000 computer and provide the same functionality. > Some of my testing runs to (temporarily) 100GB+ for input and output >files. I run it on the PC because the space isn't available on the > mainframe, but It would be nice to be able to run it on z/OS. If you get > a few users with usage spikes to 100GB the space might not be so trivial. What possible business benefit is there to running on z/OS instead of a PC when you are the only user of this file? If multiple users want to do similar things at the same time, then it's time to consider some coordination. >> gil answered that one... if you really have a good reason to go poking >> around in users' business. > HSM recalls are the big problem with that. And authorized_keys is the > sort of question where auditors might require you to be poking around in > users' business. If HSM recalls are a problem, then someone didn't talk to the z/OS storage admin. He's the one who has the knowledge and tools to handle extreme situations. z/OS is about RAS (Reliability, Availability and Serviceability). Consider the same situation on Unix where RAS is not a concern. You fill up a filesystem and disrupt every user on that system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
