It turns out that it's being limited by the authorization list (*AUTL) that secures the base dir (and all sub-dirs & files). That explains why it affects every user trying to write to that dir.

IBM says *AUTL have a 50 million object limit. The *AUTL was created solely for that dir and doesn't secure anything else. The dir shouldn't be anywhere close to 50 million files. I'm going to list all of the objects secured by this *AUTL overnight.

Thanks




-----Original Message-----
From: Jack Woehr [mailto:jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, April 15, 2019 1:10 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: IFS limits

Probably all users get the limit because w/r/t that "same directory", the "object" is owned by the one user regardless of how many users are permitted to access it via the juxtaposition of object authorities and POSIX permissions.

On Mon, Apr 15, 2019 at 12:04 PM Rob Berendt <rob@xxxxxxxxx> wrote:

Group profile perhaps?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.