CHGJOBD or CRTJOBD and ALWMLTTHD(*YES) -- MIDRANGE-L

Subject: CHGJOBD or CRTJOBD and ALWMLTTHD(*YES)
From: rob@xxxxxxxxx
Date: Thu, 3 Sep 2015 07:22:25 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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

By reading the post at
http://archive.midrange.com/midrange-l/200502/msg00619.html
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
detriment.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CHGJOBD or CRTJOBD and ALWMLTTHD(*YES) , Charles Wilt

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.