× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 04-Jun-2011 12:05 , Tom Hightower wrote:

<<SNIPped to just:>> Paragraph 2 went completely over my head :)

CRPence on Saturday, June 04, 2011 12:29 PM wrote:
<<SNIPPed to just paragraph 2:>>
The "package location" information [DBXPLOC of QADBPKG, or
LOCATION or PACKAGE_CATALOG of SYSPACKAGE] will indicate 'QSQPRCED'
for those which are created by the Extended Dynamic API, and either
the *LOCAL RDB name or a remote Relational Database name for the
others.


The SQL catalogs contain information about the SQL packages. That information is available from the SQL catalog VIEW SYSPACKAGE in QSYS2 [maybe something else or same in SYSIBM too], which is defined over the system database cross reference file QADBPKG. A query from which to infer more about the prior comments:

select LOCATION from QSYS2/SYSPACKAGE
where SYS_DNAME=:LibName /* SYSTEM_PACKAGE_SCHEMA */
and SYS_NAME=:SQLPKGname /* SYSTEM_PACKAGE_NAME */

For that query using the subject package name and the library where that package resides as replacement values for the host variables, I suspect the result string for LOCATION is "QSQPRCED" which indicates that the package was created using the API by that same name, and the *SQLPKG object would be created again when a CONNECTION to the database is made again eventually.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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.