Re: Object Authority Issue - Sometimes

[Jerry Adams <jerry@xxxxxxxxxxxxxxx>]

Rob,

You were correct about the "Create Authority" value on the libraries.  
Both project and production have *SysVal.  And the system value for 
QCRTAUT is *All. 

However, that does not (to me) explain why two different tables in the 
same library would have different authorizations.  (I do see, after 
reading my own explanation, that I failed to point this out.) 

I did run another test, though.  After I created a test table using 
iNav's Database...Schema (New Table) function, the permission on the 
table was *Public = Exclude.  Deleted the table and compiled it from the 
saved DDL.  The *Public authority is now *All.  I see nothing during the 
iNav process nor in the DDL itself that would cause the authority to be 
Exclude (or All, for that matter).

Based upon the library's "Create Authority" value, I would have expected 
*Public = All.  Why would the *Public authority be set one way when 
using iNav and another when compiling from source?  I did not find a 
setting in iNav or its Create New Table function that would override (in 
my opinion) that library's setting.

Obviously I have missed something somewhere somehow. 

	* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
	615.995.7024
fax
	615.995.1201
email
	jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



rob@xxxxxxxxx wrote:
> Prompt CHGLIB on that.  What do you have for "Create authority"?  Let me 
> guess, *SYSVAL and QCRTAUT is set to *ALL.
> I recommend changing "Create authority" to some authorization list. That's 
> supported.
>
> Rob Berendt
>