Re: multi-tenant issues with stored procedures

On Tue, Nov 28, 2017 at 2:23 PM, <dlclark@xxxxxxxxxxxxxxxx> wrote:

Besides which, our philosophy here
is that such environmental issues need to be maintained close to the
source rather than requiring each caller to have intimate details about
how the environment needs to be set up.

Are all of your stored procedures stateless? I would assume so. A Job's
library list is fundamental to the maintenance of its database state.

If so, how does that impact your overall application architecture?

To put the question in context, consider the way that the 5250 interface
facilitates multi-tenant applications. Upon successful login a Job is
launched that supports a persistent connection and a stateful session
without any extra programming or work required in order to manage session
state. The library list for each user (tenant) is established upon a
successful login through the Job Description or Initial Program call
defined in the user profile.

In my opinion, the application architecture was key to the development and
maintenance of broadly-scoped applications, where support for multiple
tenants was built-in.