Re: SQL package public authority

Gary Monnier wrote:

>Ok, CARRIE being the owner implies the 
>package is created under her profile.  Now, 
>how is *PUBLIC authority on library QGPL set?  

QGPL's public authority is *CHANGE, but I thought that only limits what I
can do with QGPL, not the authority that objects created there inherit.
QGPL's LIBCRTAUT is *SYSVAL and system value QCRTAUT is *CHANGE.

>If it is *EXCLUDE this is why your package 
>is being created with *EXCLUDE authority.

I tried creating a package in a library whose public authority is *EXCLUDE.
The package inherited the authority from LIBCRTAUT, not the library's public
authority.

The problem here is that the same function (CRTSQLPKG) works differently
when I run it explicitly as opposed to when the system runs it for an ODBC
request.

Buck Calabro
Aptis; Albany, NY
"We are what we repeatedly do.
 Excellence, then, is not an act, but a habit." --Aristotle


Billing Concepts Corp., a NASDAQ Listed Company, Symbol: BILL
+---
| 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
+---