Re: multi-tenant issues with stored procedures

You didn't say if this is a production program or some kind of one off
thing. I will assume production.

What I would think about is writing a single Service Program that gets
called each time passing parameters. This could also be a program but I
always use service programs because they are much faster.

Then I would create service program for each function and I would load them
dynamically. I believe what you are saying is that which program to execute
is not determined until run-time which is perfect for dynamically loading
service programs. When you run the RLSVSP it will return you a pointer to
the service program based on the current library list and then a activation
mark and procedure pointer.

If you are unfamiliar with dynamic service programs you find service
programs at www.think400.dk/downloads.htm, second item down.


On Mon, Nov 27, 2017 at 2:22 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

All,

Sorry for the crappy title, but I've not yet dug into the issue myself...

However, I've been told that we've had problems in the past with external
apps calling (external) stored procedures when the library list needs to
change between calls.

This is my first experience with multi-tenancy, but I know so of you on the
list have the same architecture.


Key points, the library list change affects not just the data library but
the program library also (as our customers may be on different versions
)

I think in the past, what we've tried is
my_sp ext stored proc for myrpgpgm

Where my_sp is defined in a global library and myrpgpgm is supposed to be
called from a version specific library (using the library list)

I'm curious as to how others deal with multi-tenancy.

Also I suppose, I'd like to find out more about when external stored
procedures are resolved and more importantly re-resolved?

Thanks!
Charles
--
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