Order Job (Ignore Scheduling Criteria)

The Order Job parameter forces an individual job or all jobs in a folder to be placed in the Active Jobs file (regardless of each job’s Scheduling criteria) when the On Statement/Code criteria are satisfied. This can be done on a local Control-M/Server or on a remote Control-M/Server.

Order Job causes the specified job to be placed immediately in the Active Jobs database. The job is submitted for execution as soon as all its submission criteria are satisfied.

Additional information	Description

Usage	Optional
Format	Select Order Job from the Do list box. The Control-M, Folder, Job Name, and Date text boxes are displayed. These sub-parameters are described below.
Variable Support	None For a Do Force action, you can force a job that belongs to a SMART Folder by setting the INTO_TABLE_ORDERID to one of the following: LEGACY: Forces the job into the SMART Folder of the job executing the Do Force action. The forced job must be defined within the same SMART Folder. NOTE: If the Jobname field is empty, you can force a different SMART Folder. All the jobs and Sub-Folders in the SMART Folder are forced. <Order ID of an existing SMART Folder>: Forces the new job into the SMART Folder of the specified Order ID. The forced job must be defined within the same SMART Folder. ALONE: The new job is forced individually. The job does not belong to any SMART Folder. NEWG: Forces the job into a newly created SMART Folder. LAST: Forces the job into the last ordered instance of the SMART Folder in Active Jobs. NOTES: If the forced job does not belong to any SMART Folder, the INTO_TABLE_ORDERID parameter is ignored and the job is forced individually. If the INTO_TABLE_ORDERID parameter is not defined and the Jobname parameter is empty in the Do Force action, then the NEWG value is used. If there is a Jobname in the Do Force action, then the ALONE value is used.
Alternate names	Control‑M/EM Utilities: FORCEJOB Control-M Report: (none) Control‑M/Server Utilities: ‑forcejob Control‑M for z/OS: FORCE JOB Control‑M/EM API: force_job
Alternate formats
Control‑M/EM Utilities	FORCEJOB consists of the DSN, FOLDER_NAME, NAME, and ODATE sub-parameters. The value of DSN is the Folder Library name, which must be specified for z/OS jobs. EXAMPLE: <FORCEJOB DSN="z/OS.FLD" FOLDER_NAME="fld1" JOB="Job3" ODATE="DATE"/>
Control‑M for z/OS	ORDER JOB consists of the FOLDER, NAME, and LIBRARY sub-parameters. The value of DSN is the Folder Library name, which must be specified for z/OS jobs.
Sub-parameters
Control-M	List of remote Control-M machines. NOTE: Only Control-M/EM versions 9 and above are supported.
Library	Auto-populated for Control-M for z/OS
Folder	Name of the job folder
	Length	1 through 20 characters
	Invalid Characters	Blanks; single quotation marks OS/900: Non-English characters
Job Name	Job name. If this field is blank, all jobs in the specified folder are forced.
	Length	Computers other than z/OS: 1 through 64 characters. z/OS: 1 through 8 characters.
	Invalid Characters	Blanks (embedded); single quotation marks
Date	Value to be used as the original scheduling date for the job. Valid values are:
	ODAT	Resolves to the original scheduling date of the job resulting in the execution of this parameter (default). NOTE: As of Control-M/Server version 6.1.03, ODAT can also be specified when modifying details of a job in the Active Jobs database.
	date	A date reference, 4 or 6 characters long (either mmdd, ddmm, yymmdd, or yyddmm format, depending on the site standard). z/OS: Only the yymmdd or yyddmm format can be used

NOTES:

When Order Job forces a job that belongs to a SMART Folder, it treats it as a regular job and forces it alone (that is, without a SMART Folder)
When Ordering a job on a remote Control-M/Server, the action is asynchronous. Both the action itself and variables are passed on to the remote Control-M server. If communication is down between the local and remote servers, the request will be sent once the remote server is up again. A check will be made every 48 hours
If multiple On/Do actions have been defined on a remote Control-M/Server, the order in which they will be forced on the remote Control-M server may not reflect the order of the On/Do actions. So On/Do action #2 may be forced before action #1.

Parent Topic

On/Do Actions