Re: MAPICS file authorities

["Dave Shaw" <daveshaw@xxxxxxxxxxxxx>]

It won't help you this time, but if you want to save having to get exclusive 
locks on the files when authorizing new users in the future, you could set 
all the files to use an authorization list.  You can add, change, and delete 
user authorities on an aut list dynamically, without lock contention.  Where 
I used to work, we had aut lists for several different categories of files, 
including 'anyone can see', 'only available to important people', and 'burn 
before reading' ;), and just attached the appropriate aut list to each file.

Dave Shaw

----- Original Message ----- 
From: "Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>
To: "MAPICS ERP System Discussion" <mapics-l@xxxxxxxxxxxx>
Sent: Friday, June 08, 2007 11:01 AM
Subject: Re: [MAPICS-L] MAPICS file authorities


> Thanks I saw that about CHGOWN too.  My issue with both CHGOBJOWN and 
> GRTOBJAUT is the exclusive locks required.  I guess I have to put time in 
> on Sundays to do this.  And once I do it, how do I get a custom report of 
> users with *USE authority for the files in AMFLIBE.  That is, how do I 
> check my work?  If I print a PRTPVTAUT, it shows every file in AMFLIBE as 
> having *PUBLIC *CHANGE.  I don't want to see *PUBLIC.
> Bryan