IBM OS/390 User Manual

Page of 673
10.3.3 Job Scheduling
POWER and JES2 both manage the job input queue and manage the job
selection for execution according to job classes, priority and in the order they
were submitted. In addition, OS/390 V2R4 provides additional capability with the
workload management of batch jobs according to installation specified
performance objectives.
Table 12. POWER/JES2 Job Scheduling Comparison
Job Scheduling
Function
VSE/POWER
MVS/JES2
MVS/JES2 Comments
Job Selection Priority
(Ranges)
Y
 (0 - 9)
Y
 (0 - 15)
Job Classes
A-Z, 0-n
n = n u m b e r
of partition
A-Z, 0-9
0-9 are treated just
like letters
System Affinity
Y (via SYSID)
Y (SYSAFF)
Also see WLM
Resource Affinity
Scheduling
Environments
Job Disposition
(D/H/K/L)
Y
H O L D = Y E S
See 10.3.3.1, “Job
Stream Disposition” 
Schedule on a specific
system
Y
Y (SYSAFF)
Also see Resource
affinity scheduling with
WLM in OS/390 V2R4
Time Event Scheduling
Y
N
Use a job scheduling
package like OPC.
10.3.3.1 Job Stream Disposition
The VSE/POWER job dispositions are as follows:
D
DELETE after processing.
H
HOLD job. The job remains in the reader queue, it is not dispatched by
VSE/POWER until the operator changes the disposition to D or K.
K
KEEP after processing. The job will be automatically scheduled by
VSE/POWER according to its class and priority. After job execution, the
read queue entry is not deleted from the read queue, but the disposition
becomes L.
L
LEAVE in queue. The job remains in the read queue; it is not dispatched by
VSE/POWER until the operator changes the disposition (LEAVE = HOLD +
KEEP).
OS/390 Solution
Equivalent functions for disposition KEEP/LEAVE can be obtained via procedures
causing an automatic resubmit, for example new read-in of the job as the last
step using the internal reader function.
See 10.1.1.1, “KEEP Disposition for Pre-Execution Jobs” on page 207.
Chapter 10. POWER and JES2
213