× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



iSeries IFS authority does not work the same as Windows. When you place
a file in a directory, it does not automatically inherit permissions
from the directory. Using authorization list will fix this. It also
makes it real easy to add new users without having to touch every file.
It is both good and bad in my opinion.



Chris Bipes
Director of Information Services
CrossCheck, Inc.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Odom
Sent: Thursday, January 22, 2009 10:42 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Authority to READ files in a shared subdirectory of the Root

I've created a shared subdirectory off the IFS Root and have excluded
PUBLIC but have granted "read" to a specific userid. That userid can
access the shared directory and sees the files in it but gets access
denied when she tries to read any of the files. What gives? I thought
if you give a user read to the shared directory they'd be able to read
any of the files therein. The files in the directory will be deleted
everyday via the RMVLNK command the new ones copied in via a REXX
program using FTP and MGET.

IBM says the answer is to create a AUTHL for that shared directory.
Seems like an extra step that shouldn't be necessary. Appreciate your
help and insights on this.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.