Re: Forcing batch jobs to run sequentially when batch is set up to run multiple jobs concurrently? -- MIDRANGE-L

Subject: Re: Forcing batch jobs to run sequentially when batch is set up to run multiple jobs concurrently?
From: dlclark@xxxxxxxxxxxxxxxx
Date: Tue, 16 May 2017 13:00:55 -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>

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 05/16/2017
12:59:52 PM:

Set up your subsystem and job queue to single-thread by a specific run
priority (like 6). Set the max-active jobs for priority 6 to be '1',
and submit the jobs with runpty(6).

Oh, didn't know you could do that. Nifty.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Forcing batch jobs to run sequentially when batch is set up to run multiple jobs concurrently? , Jeff Crosby

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