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



On 10/30/2017 10:47 AM, Rob Berendt wrote:
When you set up security on a library you can do
CHGLIB LIB(MYLIB) CRTAUT(MYAUTL)
So that all new objects created in that library have the authority in that
authorization list.

Is there some way to do this with an IFS directory?
Basically I want all new files, directories, subdirectories thereof, etc,
created in the '/SampleDirectory' to have the authority of authorization
list MYAUTL.

It took me a bit of digging to find The Fine Manual entry that covers
this scenario. For 7.3:
Security > Planning and setting up system security > Planning your
security strategy > Planning resource security > Planning integrated
file system security > Security for new objects, whew. The salient line
is this: 'When you create a new object in the root (/) file system, the
interface that you use to create it determines its authorities.'

The bigger picture is that the root file system tried very hard to be
true to the Unix-like security model, which has no clue about an
authorization list. So applications like 'touch' will inherit the
Unix-y parts of the authority model, but not the 'native' bits.

I note that contrary to this generality, the open() API will inherit the
authorization list. Here is a very hacked together RPG program that
will 'touch' a file and inherit the security from the parent directory:
https://code.midrange.com/fb71679356.html


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.