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
This mailing list archive is Copyright 1997-2019 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