My gut feeling is that it'd be a bad idea....but I don't have any specific
reason why.

I do note that the help text says, "This attribute should be set to *YES
_ONLY_ in job descriptions used exclusively with functions that create
multiple user threads." (emphasis added)

Note the word ONLY...


On Thu, Sep 3, 2015 at 7:22 AM, <rob@xxxxxxxxx> wrote:

Any reason not to use ALWMLTTHD(*YES) on your job descriptions?

By reading the post at
I see that if a particular job type (ie interactive) doesn't like it it
will just not use it. Not that it rejects the job or anything.

I'm sure there's the usual disclaimers about whether or not that job
actually performs better being multithreaded, or whether or not it has any
adverse effects on other jobs.

I am wondering if we just keep copying QDFTJOBD to create new job
descriptions and carrying on a legacy technique, and if that is to our

Rob Berendt
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755

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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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.