Tweet
The methods for default authorities on new database files are AUT(*LIBCRTAUT) per CHGLIB CRTAUT(), and there are authority holders per CRTAUTHLR. The former is true of most external object types. Each is dependent upon, into which library the file is placed. Regards, Chuck Comments provided "as is" with no warranties of any kind whatsoever.
-
-
file security
On Tuesday, October 13, 1998, 01:28 PM, Camille C Childers wrote: Some of our users create queries that output files. These files are created with their user profile having *all authority and *public with *change authority. Is there any way to have these files created with *public *exclude, or will I have to output these to a different library. Camille, Are these being run with RUNQRY? If so specify AUT(*EXCLUDE). You could probably change the command default. I don't know if this would affect the WRKQRY command. Your users could be instructed that they should specify *EXCLUDE when they create a query. If you subscribe to the users own the data theory, it should be their responsibility to specify *exclude on the output screen select output type and output form screen. If they don't... they own the data. The alternative would be to use the RUNQRY and WRKQRY defaults and change the creation authority on your library CHGLIB lib CRTAUT(*EXCLUDE), or output to a library with crtaut(*exclude). David Morris
Comment