Re: SQL package public authority

Ok, CARRIE being the owner implies the package is created under her profile.
Now, how is *PUBLIC authority on library QGPL set?  If it is *EXCLUDE this
is why your package is being created with *EXCLUDE authority.

----- Original Message -----
From: Buck Calabro <buck.calabro@aptissoftware.com>
To: <MIDRANGE-L@midrange.com>
Sent: Thursday, June 29, 2000 2:15 PM
Subject: Re: SQL package public authority


> Gary Monnier wrote:
>
> >> Buck Calabro wrote:
> >> I have an interesting question regarding the public
> >> authority the system gives to a newly created SQL
> >> package.
> -snip-
> >> The nominal fix is to delete the package and let the
> >> machine create a new one, which it does.
> >> Unfortunately, at one site, it is created with AUT(*EXCLUDE).
>
> >What profile is creating the package?
> >Is it Carrie, or some other profile?
>
> CARRIE is the owner.  OS/400 is creating the package.
> Again, this is not a problem when anybody creates a package using
CRTSQLPKG.
> It is only a problem when the package is created by OS/400's ODBC support.
>
> Buck Calabro
> Aptis; Albany, NY
>
>
> 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
> +---

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