Control Resources

(From Forecast only) Indicates the resources required by the job during execution and the type of control (shared or exclusive) the job requires over each resource. The Control Resources parameter is used to control parallel execution of jobs.

Additional information	Description

Usage	Optional NOTE: A maximum of 99 Control Resources can be specified for a job.
Length	1-64 characters z/OS: 1-20 characters
Case Sensitive	Yes However, if the Uppercase Only check box was selected in the Add Control‑M Definition window, you cannot use lowercase characters.
Invalid Characters	Blanks Computers other than z/OS: Single quotation marks
Variable Support	None
Alternate names	Control‑M/EM Utilities: CONTROL Control-M Report: RESOURCE Control‑M/Server Utilities: ‑control Control‑M for z/OS: CONTROL Control‑M/EM API: control_resource
Alternate formats
Control-M Report	The Control Resources parameter is composed of the sub-parameters below.
	RESOURCE	Name of the resource. String.
	TYPE	Type of Control resource: E - Exclusively owned by a job S - Shared by any number of jobs
Sub-parameters
Resource Name	Defines the name of the Control resource.
	Length	From 1 through 64 characters
	Case Sensitive	Yes However, if the Uppercase Only check box was selected in the Add Control‑M Definition window, you cannot use lowercase characters.
	Invalid Characters	Blanks; single quotation marks.
Type	Shared Exclusive
On Fail (z/OS)	Release Keep

If a job requires exclusive use of a Control resource, only that job can use the Control resource. If another job requests the same resource in exclusive or shared state, this second job is not submitted by Control‑M until the resource is released by the first job.

If a job requires a Control resource in shared state, that job can run in parallel with other jobs that request the same resource in shared state.

EXAMPLE: Scheduling a job using an exclusive resource

Job R1 (which reorganizes a disk) cannot run in parallel with job B1 (which backs up the same disk) or job B2 (which reads data from the disk). Jobs B1 and B2 do not interfere with each other and can be executed in parallel.

Job R1 is defined as follows:

File name = R1

Control Resources: VS01 = E
Job B1 is defined as follows:
File name: B1
Control Resources: VS01 = S
Job B2 is defined as follows:
File name: B2
Control Resources = VS01 = S
Jobs B1 and B2 can run simultaneously since they both use resource VS01 in shared mode. Job R1 requests VS01 for exclusive use and therefore cannot run in parallel with either job B1 or B2.

If either job B1 or B2 is running, Control‑M does not submit job R1.

If job R1 is running Control‑M does not submit job B1 or B2.

Control‑M submits job B1 if job B2 is running, and vice-versa.

Parent Topic

Prerequisites parameters