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
IBM Certified System Administrator - IBM i 6.1
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
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.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.