Re: SQL package public authority

>> Objects created under the *SQL naming are AUT(*EXCLUDE).
 >> Objects created under the *SYS naming are AUT(*LIBCRTAUT).

 > Is this behaviour documented somewhere?  I couldn't find where AUT
 > comes from on CRTSQLPKG.

I think the AUT parameter on a package comes from the naming convention
used when compiling the program.
The security in SQL environment depends totally of the naming:
 - with *SYS naming, all database objects are AUT(*LIBCRTAUT), and the
programs/packages are USRPRF(*USER),   (BTW following the standard AS/400
behaviour)
 - on the other hand,  with *SQL naming, all database objects are
AUT(*EXCLUDE), and the programs/packages are USRPRF(*OWNER).
IMHO, it makes sense.  But problems arise when the 2 namings are used
concurrently...
HTH
Best regards
Richard THEIS
AS/400  Education
  theis_richard@fr.ibm.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---