RE: Automatically Moving Jobs Around

No need for different *JOBQ names.

Set different activity levels for *JOBQ QBATCH in subsystem QBATCH, based on priority.

Like this:

CHGJOBQE SBSD(QBATCH) JOBQ(QBATCH) MAXACT(7)
MAXPTY3(*SAME) MAXPTY4(2) MAXPTY5(1) MAXPTY6(3)


Execute WRKSBSD QBATCH and take Option 5 then Option 6 ... You'll see this:

Display Job Queue Entries
System: S02
Subsystem description: QBATCH Status: ACTIVE

Seq Job Max ---------Max by Priority----------
Nbr Queue Library Active 1 2 3 4 5 6 7 8 9
10 QBATCH QGPL 7 * * * 2 1 3 * * *

The priority for a BATCH job is initially set by the *JOBD and usually is defaulted to 5.

Job description: QBATCH Library: QGPL

User profile . . . . . . . . . . . . . . . . . . : *RDQ
CL syntax check . . . . . . . . . . . . . . . . : *NOCHK
Hold on job queue . . . . . . . . . . . . . . . : *NO
End severity . . . . . . . . . . . . . . . . . . : 30
Job date . . . . . . . . . . . . . . . . . . . . : *SYSVAL
Job switches . . . . . . . . . . . . . . . . . . : 00000000
Inquiry message reply . . . . . . . . . . . . . : *RQD
Job priority (on job queue) . . . . . . . . . . : 5

All the "user submitted" jobs will go to *JOBQ QBATCH with a priority of 5 and will now single thread.

You can easily change any job on the job queue using the CHGJOB JOB(nnnnnn/xxx/xxx) JOBOTY(n) command or directly from the WRKJOBQ command via Option 2 (Change)

Submit anything you would like to run outside of the default setting of 5 to run at another job queue priority. It will then run concurrently with jobs running at other priorities.

For example: SBMJOB CMD(my_command) JOB(JOBNAME) JOBD(QBATCH) JOBQ(QBATCH) JOBPTY(6)

Jobs submitted with JOBPTY(6) will run 3 concurrent jobs as long as the Max Active setting for the *JOBQ and Subsystem Activity level aren't exceeded...

There is an API: Retrieve Job Queue Information (QSPRJOBQ) that could be used to gather up *JOBQ entries and change JOBPTY based on some rules in your code... but I think it would be a lot easier to change the JOBPTY on different *JOBD's and then use the appropriate *JOBD when you submit the jobs in the first place.

This explanation was more complicated than I thought it would be... I hope it makes sense..

Reply or Forwarded mail from: Kenneth E Graap


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Monday, August 03, 2015 12:33 PM
To: 'Midrange Systems Technical Discussion'
Subject: [External]RE: Automatically Moving Jobs Around