🚀 go-pugleaf

>big IBM fan  is this read concept.   It is almost as outmoded  as card readers
Ah, er, um... most multi-user systems today have some sort of spool
concept. It may not be called spool, but it is still there. It might
be some sort of (to use an AppleShare term) "drop box", but it is
really the same thing. It is not limited to IBM and it is in my opinion
far from outmoded.  I sure don't want to give everyone write access to
all my files/directories.

>think the reader here  has a capacity of 30,000 files which is  fine for us at
>Temple, but might be miniscule for many other sites.
CP supports many more than that (not sure what the upper limit is, but
I believe it is 'hugh' by comparison to 30K).  The limit is affected by
how the system is configured (we're talking VM/XA or VM/ESA here), so a
site can set a lower system wide limit.  Each user has a max limit of
10K, but for most users (other than perhaps RSCS) this isn't a problem.

>better to  set a  limit on  the number  of files  that can  reside in  any one
>person's reader list.
This support exists as a CP Directory entry. I don't personally think
it solves this particular problem nicely. I'd prefer seeing MAILER being
able to write to an SFS directory for the user and having mail/mailbook
get new mail out of there (as well as the spool). There should also be
user controls added to SFS to allow the end user to limit the amount
of data that can do into such a directory. This would give the end
user control over these matters, and more easilly allow chargeback
of space used to those using it.