We have the same issue as Rob has pointed out.
There are several options.
1) Create a separate single threaded jobq for those long running jobs, so as to not hold up shorter jobs in QBATCH.
2) If allowed (after researching if jobs can be single or multi threaded) create a new multi- threaded jobq.
We actually got away from using QBATCH (jobq and subsystem) , and QINTER subsystem.
We have separate multiple jobqs (some single, some multi) for each application.
All our batch subsystems start with BATCH_**.
When you do a WRKACTJOB, all batch jobs will be on first screen, top of the list.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, August 03, 2015 3:10 PM
To: Midrange Systems Technical Discussion
Subject: Re: Automatically Moving Jobs Around
Sounds great in theory. However, is QBATCH single threaded? If so, are some of those jobs counting on that?
JOB1-Save 'before' to tape
JOB4-Save 'after' to tape
Nope, taking too long, let's balance them out to multiple job queues and/or subsystems and let them all run at once.
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
Kendallville, IN 46755
From: "Bakutis, Becky" <BBakutis@xxxxxxxxxxxxxxxxxxxx>
To: "midrange-l@xxxxxxxxxxxx" <midrange-l@xxxxxxxxxxxx>
Date: 08/03/2015 02:54 PM
Subject: Automatically Moving Jobs Around
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
1. Is there an API that can automatically transfer control of a running
batch job to another subsystem?
2. During month-end we have a large number of user-submitted jobs that
automatically go to the QBATCH job queue and hold up other jobs. Is there
a way to automatically redirect jobs to a different subsystem once they
hit the job queue?