|
Hi Nathan
On Thu, Nov 30, 2017 at 10:02 AM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:
Are you looking at the user it is runnign under or the "Current User"
a different user id would allow for a different job description to
be used and, therefore, support multi-tenancy. Am I off-base here?
I'm not sure whether you're off base, or not. As I review the QZDASOINIT
Jobs on a couple client boxes, I see Jobs that are running under a number
of different User Profiles. But they are all running under the same Job
Description. As far as I could tell, they all have the same library list.
value.
My understanding is this: When the users connect to the QZDASOINIT job in
any given subsystem then they will pick up the job description associated
with the Job by the Pre Start Job Entry.
Changing the Job Description in the pre-start job entry would allow you to
substitute a more appropriate job description for the connection rather
than the default QGPL/QDFTSVR value.
Having multiple subsystems for multiple connections classes (i.e. tenants)
would allow for customization of the job description on a tenant-by-tenant
basis - one description per subsystem.
--
Regards
Evan Harris
--
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
As an Amazon Associate we earn from qualifying purchases.
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.