The issue is not necessarily the collections and the package sets, it is also user
related. Who are you connecting as and who is granted access the packages.

For instance:

EXEC SQL CONNECT TO 'yourdb' USER 'fred' USING 'freds_password';
EXEC SQL SET CURRENT PACKAGESET 'Coll1';

This will set the user and the package set to be a know value. In your case, you would
have to have bound the package as follows:

DB2 BIND CSAPACK1.BND GRANT_USER fred;

Thus, when fred signed into the system, he would implicitly select the collection 'Coll1'
and fred would have the rights to use this package.

Richard Reppert
Sumx, Inc

On Thu, 20 Mar 2003 14:16:51 -0600, trace.[Email Address Removed] wrote:

>We have this scenario right now:
>
>Collection
>
>Coll1
>Coll2
>Coll3
>
>Packages
>
>CSAPACK1
>CSAPACK2
>CSAPACK3
>
>Same 3 package names exist in all 3 collections
>
>Qualifiers
>
>CS1 - match to coll1
>CS2 - match to coll2
>CS3 - match to coll3
>
>We are getting a -805 (missing dbrm) when they are trying to run their
>programs. Are we stepping on DBRMs?
>
>T. Jones
>
>
>---------------------------------------------------------------------
>PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
>To unsubscribe, e-mail: db2udbdba-[Email Address Removed] additional commands, e-mail: db2udbdba-[Email Address Removed]DB2 & UDB email list listserv db2-l LazyDBA home page