On 28-Aug-2015 09:25 -0600, Bobby Adams 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
I hope that I am just overlooking something obvious and am hoping
somebody else has experienced this before and can point it out.
A generic provider asking to perform the equivalent of a SQLTables()
request is essentially just returning the data from the SYSTABLES VIEW
[from either QSYS2 or SYSIBM]; i.e. just a result-set as a query of that
VIEW. In effect, the DB2 for i considers the /system/ to be the
/database/, thus [somewhat oversimplified,] all entities for all
libraries across the system are made visible; though possibly limited
only to those entities authorized to the user, AIUI, depending on which
catalogs are accessed.
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.
The Default Schema does not affect what is presented, only where
certain unqualified references will search for the entity with the
The Job Description (JOBD) and the User Library List (USRLIBL) are
primarily for establishing an interactive 5250 session. Yet even if
utilized for other types of connections, e.g. ODBC\JDBC, the SQL
database catalog API requests would need to be limited accordingly.
However, a generic provider does not know the concept of a Library List
(LIBL) of the IBM i, and presumably merely effects a query of the
appropriate catalog VIEW. There would need to be an effective LIBVIEW
against which the server could be requested to limit the output from the
API calls [to a specific list of libraries]; see my reply referring to
documentation that might assist [in part, just for IBM® i Access ODBC