I'm pretty sure you can delete any *sqlpkg that doesn't start with a 'Q' :
such as qzdapkg, qsqlpkg2, qsqxdpkg;  these must not be deleted



                    "Steve McKay"
                    <Steve.McKay@SouthT       To:     midrange-l@midrange.com
                    rust.com>                 cc:
                    Sent by:                  Subject:     *SQLPKG question
                    midrange-l-admin@mi
                    drange.com


                    01/31/02 03:19 PM
                    Please respond to
                    midrange-l







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.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.