Gil,
If I read your entry correctly you are incorrect. OS/360 *DID* have
enq/deq facilities (on the same system ) So on the same system you
could simply not delete a data set that was in use.
The cross system is more or less true albeit a small exception for
GDG's but that was at the cvol level not dataset,
Ed
On Nov 27, 2012, at 11:25 PM, Paul Gilmartin wrote:
On Tue, 27 Nov 2012 17:12:01 -0800, Edward Jaffe wrote:
I have heard of filesystems that implement space quotas.
That's per user, of course. But MVS grew out of OS/360, which had
little concept of resource ownership, and has not well matured beyond
that. For example, if I own a data set, I ought to be able to
delete or
rename it, even if the consequence is preempting other users who may
happen to have it allocated.
But user quotas is a much less cumbersome scheme than requiring a
user to specify SPACE= on each individual data set. Given the
essential
corollary of effective reporting ("How close am I to exceeding quota,
and what data sets are the major offenders?") z/OS Unix System
services (USS) does pretty well here, by giving each user a zFS
partition
and letting that user subdivide it as desired. du(1) is a reasonably
effective reporting tool.
-- gil
----------------------------------------------------------------------
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
