It sounds like he wants some parts to be able to run at the same time, The
different *JOBD's can help him. But if the jobs are submitted, He can just
change the submit command to go the job queue's.
That being said If your company will allow, it is possible to thread your
JOBQ's by priority, I've seen it done in an EDI JOBQ. We were single
threaded by priority, but could have up to 5 jobs from the JOBQ running at
a time. I would be wary of doing the same structure to QBATCH.
From:
"Graap, Kenneth" <Kenneth.Graap@xxxxxxxxxxxxx>
To:
"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:
04/14/2009 07:45 AM
Subject:
RE: Splitting QBATCH
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
I'd suggest that you just use one queue, QBATCH but different job
priorities....
Control the job priorities for each kind of job through the use of
different Job Descriptions (*JOBD)
Kenneth
Kenneth E. Graap
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tomasz Skorza
Sent: Tuesday, April 14, 2009 5:25 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Splitting QBATCH
Hi
have you any idea how to dividing jobs which by default goes in QBATCH
into two(or more job queues) depending on name of job, user id etc? So
some user call some jobs and then some program check this job and decide
which job queuue should be use - default QBATCH or other i.e. reports.
Tomek
--
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.
midrange.com
