IBM manual Job Scheduling, Job Stream Disposition, OS/390 Solution

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	VSE/POWER	MVS/JES2	MVS/JES2 Comments
Function
Job Selection Priority	Y	Y
(Ranges)	(0 - 9)	(0 - 15)
Job Classes	A-Z, 0-n	A-Z, 0-9	0-9 are treated just
	n = number		like letters
	of partition
System Affinity	Y (via SYSID)	Y (SYSAFF)	Also see WLM
			Resource Affinity
			Scheduling
			Environments
Job Disposition	Y	HOLD=YES	See 10.3.3.1, ªJob
(D/H/K/L)			Stream Dispositionº
Schedule on a specific	Y	Y (SYSAFF)	Also see Resource
system			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:

DDELETE after processing.

HHOLD 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.

KKEEP 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.

LLEAVE 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 page207.

Chapter 10. POWER and JES2 213