PUBLIC would have to be *AUTL for the Authorization List to be read. PUBLIC *EXCLUDE stops the authority search right there if the user doesn't have specific access to object.
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx>
Sent: Thursday, March 12, 2026 08:14
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Authority on an IFS file
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
I have an IFS file with *PUBLIC *EXCLUDE but it also has an AUTL with
*PUBLIC *ALL. A user is getting an error saying they can't access it. I thought the AUTL
overrode the file's authority. Does *PUBLIC have authority to it or not.
Jack WoehrIndependent Consulting Programmer 303-847-8442 jack.woehr@xxxxxxxxxxx www.procern.com Stay Connected!Upgrade your IT state of mind!NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.