​I suspect that the​ interface is using one of the catalog views such as

Entire list of catalog views here:

That being the case, the client will see every library even if they don't
have the authority to use the library.

I suppose if you're on v7r2, you might be able to use Row/Column Access
Control (RCAC) to limit what can be seen by user...though I'm not sure that
would supported on an IBM provided object. Also, most the catalog views
are just that views...many times over user defined table functions. Which
IFAIK, RCAC doesn't apply too.


On Fri, Aug 28, 2015 at 11:25 AM, Bobby Adams <bobby_adams@xxxxxxx> wrote:

We are trying to evaluate the OpenLink Multi-tier Data Access product. I
have the different pieces installed and working. However, at the client pc
I can see all the libraries on the IBM i via the ODBC connection. I would
like to limit the libraries the client pcs can access to just a few. I
have tried several things but can't make it work. OpenLink support has
given me suggestions and I have tried them.

I hope that I am just overlooking something obvious and am hoping somebody
else has experienced this before and can point it out.

I have tried using a user profile that has a library list of just a few
libraries and have tried to set the default schema via the JDBC URL. Any
suggestions will be welcomed.

Bobby Adams
Frank Cawood and Associates
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


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

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