Hi Nathan

This document:
http://www-01.ibm.com/support/docview.wss?uid=nas8N1010026
Suggests it is what you are doing and how you are doing it that influences
the library list. I recall another discussion (maybe even this one) that
discussed the use of System naming vs SQL naming which appears to be quite
significant.
The choices for each system are going to be dependent on a lot of factors.



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

On Wed, Nov 29, 2017 at 3:10 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

No. Our volumes are too low to set up a separate subsystem (memory
pool, etc) for this subset of the workload.


If I understand correctly, you're saying that QZDASOINIT Jobs automatically
adopt the Job Description (including library list) that is defined in the
User Profile, when a connection is established via that User Profile?

That seems counter-intuitive to me for prestart Jobs, in that they are
already running. I do understand that IBM could put logic in the program to
change its library list to that of the currently connected user profile.
That's what Dave Clark is doing. You appear to be saying that's already
provided by IBM.
--
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 thread ...

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.