On 24-Aug-2016 10:55 -0700, Jonathan Ball wrote:
> Three-part naming is a great DRDA feature. Unfortunately, it doesn't
> work right out of the box.
>
> select authorization_name, maximum_allowed_storage, storage_used
> , text_description
> from remotesys.qsys2.user_info
> where maximum_allowed_storage is not null
> and storage_used / maximum_allowed_storage >= .75
>
> SQL State: 51002
> Vendor Code: -805
> Message: [SQL0805] SQL package QSQCLIPKGN in QGPL not found at DRDA
> Server.
AFaIK, the three-part-naming feature functions fine without any of
those packages, when that query originates on the server [with a truly
*LOCAL connection] vs when that query is requested from a client; that
has been my experience anyhow, as none of the systems on which I have
access, currently have those SQL CLI packages, and testing verifies that
there were no errors, plus the expected result-set was returned.
>
> I know how to create the packages using the DB2PackageCreator JAVA
> class (
http://www.ibm.com/support/docview.wss?uid=nas8N1017528),
> but I don't know why those packages wouldn't already exist
Perhaps seemingly odd, that some product\option installation does not
just effect the creation of those packages, but there is a legitimate
reason. That is, SQL packages are recorded locally for the creation on
the remote DRDA server. Not only must the remote server have been
registered as an entry at the local system [in the Relational DataBase
Directory Entry (RDBDIRE)], and each server properly defined with a
*LOCAL entry, but the connection to the remote servers must be available
[for which normal system ops is required at the requester, thus
post-install, and also normal system ops at the remote server], on which
the packages are created.
--
Regards, Chuck