Re: Commands For File Permissions -- MIDRANGE-L

Subject: Re: Commands For File Permissions
From: rob@xxxxxxxxx
Date: Tue, 10 May 2011 15:13:47 -0400
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>

I would strongly lean towards using authorization lists versus adding
individuals to each file. Helps avoid issues like file locks, etc.

First, use CRTAUTL or WRKAUTL to create an authorization list.
Then add users to the list with WRKAUTL.
Then change all objects in that library to use that authorization list
with
CHGAUT OBJ('/qsys.lib/mylib.lib') AUTL(MYAUTL) SUBTREE(*ALL)
Then change the authority for *PUBLIC to use that authorization list with
CHGAUT OBJ('/qsys.lib/mylib.lib') USER(*PUBLIC) DTAAUT(*AUTL)
OBJAUT(*NONE) SUBTREE(*ALL)

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

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.