Re: Locking users out of an IFS directory -- MIDRANGE-L

× 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.

Subject: Re: Locking users out of an IFS directory
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Fri, 15 Jan 2010 15:34:42 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

James H. H. Lampert wrote:

Scott Klement wrote:

You'd need DTAAUT(*RX) rather than just *R.

Except that DTAAUT(*R) was the first thing I tried, before I even bothered the List, and it didn't stop the user from creating a file in the directory.

Oops. DTAAUT(*RX) was the first thing I tried.

DTAAUT(*R) appears to block new file creation, but at the cost of causing other problems.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Locking users out of an IFS directory , Scott Klement

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.