Re: Automatically Moving Jobs Around

[Evan Harris <auctionitis@xxxxxxxxx>]

Hi

If the batch job is actually running there is no way that I know of to
transfer it to another subsystem other than cancelling it and restarting it.

I have had the same problem as you with user-submitted batch jobs. The
solution in my opinion is to create the required jobqs and perhaps
subsystems to manage the work as others have suggested, but it's also
important to look at the jobd's the users are using and how they are
submitting jobs - this is what causes everything to end up in the one job
queue. If you fix their job descriptions - and can influence the job
submission process in some way - then any future jobs will also go to the
"right place".

It might take a while to work through the job descriptions and job queues
for the individual users but in the long terms results will probably be
better.




On Tue, Aug 4, 2015 at 6:53 AM, Bakutis, Becky <
BBakutis@xxxxxxxxxxxxxxxxxxxx> wrote:

> 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?
>
>
> --
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.