SQL package public authority

I have an interesting question regarding the public authority the system
gives to a newly created SQL package.
We have a Delphi application that uses ODBC and extended dynamic SQL.  On
occasion, we need to change the data source (library list reasons).  When we
do, the package associated with that application is "out of sync."  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).  Now, there is
no explicit CRTSQLPKG happening on a command line; when the Delphi app
connects to the AS/400, OS/400 creates a package under the covers.  Oddly
enough, there is no AUT parameter on CRTSQLPKG...

Here are the particulars:
User profile CARRIE
  GRPPRF(ACCOUNTING)
  OWNER(*USRPRF)
  GRPAUT(*NONE)
  GRPAUTTYP(*PGP)
  SUPGRPPRF(*NONE)
Package created in QGPL, which is LIBCRTAUT(*SYSVAL)
System value of QCRTAUT is *CHANGE

Why is public authority *EXCLUDE and how can I make it reflect LIBCRTAUT?

As a further tantalising anomaly, when I manually use CRTSQLPKG over one of
my RPGLE SQL programs, the public authority is based on LIBCRTAUT -- exactly
as expected.

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