Re: *SQLPKG question

I know if you create an embedded SQL program that accesses a remote
AS/400 database you must create an SQL package on the remote system for
the program to work.  If you delete the package (or it doesn't get
created properly) your program won't work.
This is a case where you the programmer have to control when and how the
package gets created not -via- some form of ODBC database access.
The package is either created based on the parameters in the CRTRPGSQLI
command or the CRTSQLPKG command.
Without going into much more detail on SQL packages, I would recommend
you are careful what packages you delete and be sure they are not
necessary for programs to function.

Brian Ellis

Steve McKay wrote:
>
> Gang -
>
> If I understand *SQLPKGs correctly, they are built via ODBC connections in
> order to speed up DB access for those connections.  True?  What would
> happen if I deleted all the *SQLPKG objects on the system and allowed them
> to be rebuilt?  (Many of the SQLPKGs indicate that they were created by
> mere users, not by the system or by any other 'powerful' profile.)
>
> I ask this because I have SQLPKG objects in QGPL *and* I have SQLPKG
> objects with identical names to those in QGPL in the data library of a
> vendor package.  I believe this is causing a problem that we are having
> with the vendor package.
>
> Any comments or suggestions are welcomed.
>
> Thanks,
>
> Steve
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.