Re: Object Authority Issue - Sometimes

Jerry Adams wrote on 02/27/2008 09:23:02 AM:

I create any new tables in our applications by using SQL's DDL.
Actually I do it through iNav's Database...Schema tree for what it's

worth.

Usually these tables come out with *Public = *All. Occasionally, they
arrive with *Public = Exclude. Why?

Potentially more info: I use iNav's "Generate SQL" function to save the
DDL to a source physical file. Sometimes I will use the RUNSQLSTM
command against said source member to create a table. Don't know if
that makes a difference. However, I just did that for a table in one of
my project libraries that had *Public = Exclude, and the table, after
"re-compiling," had *Public = All. I tried various options on the
RUNSQLSTM but it still came out as *Public = All. How it got to *Public
= Exclude is a mystery - to me, anyway.

My guess is that you are using system naming in one case and SQL naming
in the other. I have an old DB2 SQL reference manual and it says this:

Authority granted to *PUBLIC on SQL objects depends on the naming
convention that is used at the time of object creation. If *SYS naming
convention is used, *PUBLIC acquires the authority of the library into
which the object was created. If *SQL naming convention is used,
*PUBLIC acquires *EXCLUDE authority.

Ed Fishel,
edfishel@xxxxxxxxxx