Re: multi-tenant issues with stored procedures

Hi Nathan

Here is one way to route incoming connections (by user ID)
http://www-01.ibm.com/support/docview.wss?uid=nas8N1021000

The same thing can also be managed by IP address:
http://www-01.ibm.com/support/docview.wss?uid=nas8N1019587

I've used this in the past as a work management strategy but there is no
reason why you could not segregate tenants by subsystem and refuse
connections if the subsystem was not active.

Presumably if you can direct them to another subsystem you can customize
the Pre-start Job entries in those subsystems to whatever suits your
purposes.

I am not saying this a good or bad idea, I am just saying it looks like it
might be possible.


On Thu, Nov 30, 2017 at 9:31 AM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

On Wed, Nov 29, 2017 at 12:01 PM, <dlclark@xxxxxxxxxxxxxxxx> wrote:

Yes, but off-platform stored procedure calls all come into the IBM
i using the same job description -- correct?

To me the question sounds rhetorical. At the risk of stating the obvious
I'll respond by saying that off-platform applications connect with a
prestart job (QZDASOINIT, most likely) that is probably already running
within a pool of prestart Jobs that respond to such client requests.

If this is not correct.

Please enlighten me how an off-platform stored procedure call can specify
what IBM i job description to use for its session.

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.
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD