Re: SQL package public authority

[Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>]

Richard Theis wrote:

>>Buck wrote:
>>
>> 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.
>
>It has to do with the naming: your ODBC driver is 
>using the *SQL naming, and you are using the *SYS naming.
>Objects created under the *SQL naming are AUT(*EXCLUDE).
>Objects created under the *SYS naming are AUT(*LIBCRTAUT).

We are using *SYS naming on about a dozen other systems and don't have this
problem.  Is this behaviour documented somewhere?  I couldn't find where AUT
comes from on CRTSQLPKG.

Merci!
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
+---