× 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.


  1.  Home
  2. MIDRANGE-L
  3. November 2017

Re: multi-tenant issues with stored procedures

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 11/29/2017
03:31:41 PM:
I'm not aware of any way for off-platform programs to "pick" which IBM i
database Job they might connect to. And I'm not aware of any way to
configure prestart jobs to service a particular tenant.

Frankly, I'm not aware of any solid rationale for trying to support
multi-tenant environments via QZDASOINIT Jobs nor any other interface
that
is based on ODBC or JDBC. Hence, the reason for my question. To open the
discussion to explore options.


Well, in our case, I know that the QZDASOINIT jobs end up running
under the user id that is sent in the connection from the off-platform
sources (we have up to about a dozen different off-platform sources) and,
therefore, all use the same job description. So, I presumed that coming
in with a different user id would allow for a different job description to
be used and, therefore, support multi-tenancy. Am I off-base here?


Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.