General parameters contain basic information that identifies the job, describes what it does, and gives the location of the job script.
Parameter |
Description |
---|---|
Defines the type of job that determines which fields are exposed in a job definition. The value of the job type is usually based on the platform for the job run. Jobs defined as Dummy provide instructions for Control-M such as post-processing actions. |
|
Defines the name of the job processing definition and appears in the job definition and tracking displays, and enables you to identify the job, and order the job. |
|
Provides a description of the job in free text. A well written description can help you determine why the job was defined and how it fits into your business workflow. |
|
Defines one or more parameters which determines what the job runs. |
|
Indicates an operating system command line entry to be submitted as a job. Use this parameter to specify an operating system command to execute by Control-M. The command must be specified exactly as it would be specified in a terminal for the specific computer. |
|
Defines a script exactly as it would be specified in a terminal for the specific computer and is part of the job definition. |
|
Defines the name of a Control-M/Agent computer, remote host computer, or host group where the job is submitted. |
|
Defines the name of the Control-M/Server (or Control-M for z/OS) that processes the job. |
|
Identifies the user name with the authorization to execute the job. This parameter is used by the Control-M security mechanism. |
|
Specifies a temporarily-modified job script file without changing the original script file in the File Path/Member library and without changing the scheduling order of a folder. |
|
Specifies a command to run immediately before running the job defined by the What parameter. The return code is ignored. |
|
Specifies a command to run immediately after running the job defined by the What parameter. The return code is ignored. |
|
Specifies that job submission details be broadcast to all agents within a defined Host Group. All available agents in the Host Group run an identical job, and each such job has a unique Order ID. |
|
A regular job submitted to Control-M for execution as a background process. The results of the job (the output) are analyzed by the post-processing subsystem. |
|
All variables are identified by the %% prefix. If %% is included in the value for a job processing parameter, Control‑M assumes that it is referring to a variable or function. |
|
Provides a logical name for sorting groups of jobs. This parameter is used to supply a common descriptive name to a set of related job groups. The jobs do not necessarily have to run at the same time. |
|
Indicates the name of the Sub Application where the job belongs logically. It is a sub-category of the Application parameter. For example, the Application is Finances, and the Sub Application is Payroll. |
|
Indicates the Control‑M/EM user who defined the job. |
|
Determines the order of job processing by Control-M in the Active Jobs database. |
|
Determines whether the job is a critical-path job in Control-M, which ensures resources allocation order. |
|
Defines the name of the Control-D Report Decollating Mission Category. If specified, the report decollating mission is scheduled whenever the job is scheduled under Control-M. |
|
For a z/OS job, Doc Library defines the name of the library where the Documentation (description) is saved. For a non-z/OS job, Doc Path defines the name of the file path where the Documentation is saved. |
|
For a z/OS job, defines the name of the member where the job Documentation (description) is saved. For a non-z/OS job, the Doc File is the name of the file where the job Documentation is saved. |
|
Defines the URL address where the documentation is located. |
|
Indicates the name of the file that contains the job script, or for z/OS jobs, the name of a member that contains one of the following in relation to the job to be executed:
|
|
Specifies that the job is invoked with the operator START command. |
|
For non-z/OS jobs, File Path indicates the location of the file that contains the script. For z/OS jobs, Member Library indicates the location of the Member that contains the JCL, started task procedure, or Warning message. |
|
Performs data set cleanup before the original job run. |
|
Defines the node in the JES network where the job executes. |
|
Indicates the JES2 workload management scheduling environment that is to be associated with the job. |
|
Indicates the identity of the system in which the job must be initiated and executed (in JES2). |
|
Defines the name of the library that contains the job’s folder. |
|
Defines the name of the folder. In the Properties pane, this parameter indicates the folder where the job belongs. |
|
Indicates whether the folder type is a regular folder, a SMART folder, or a Sub Folder. |
|
Defines the method for ordering the entity as one of the following:
|
|
Defines User Daily jobs whose sole purpose is to order jobs. Instead of directly scheduling production jobs, the New Day procedure can schedule User Daily jobs, and those User Daily jobs can schedule the production jobs. Set User Daily Name when Order Method is set to Specific User Daily. |
|
Determines whether the z/OS job is an Emergency job. |
|
Defines the first program step for a job to begin at when it is restarted. |
|
Defines the first procedure step for a job to begin at when it is restarted. |
|
Defines the last program step for a job to stop running. |
|
Defines the last procedure step for a job to stop running. |
|
Logical name, from a user or business perspective, for the critical service. BMC recommends that the service name be unique. |
|
Defines the time the critical service must be completed to be considered on time. The time can be specified either by a specific hour and/or day or on a specific hour and minute after the order time. |
|
Defines the priority level of this service, from a user or business perspective. |
|
Defines the automatic interventions, such as rerunning a job, displaying the critical service in BMC Service Impact Manager, or extending the service due time. The action is performed if the job finished too quickly, there is a job failure on service path, or the service finished late or too quickly. |
|
Defines the type of deviation from the average completion time for a job in the service. If the run time falls within the tolerance set, it is considered on time, otherwise it has run too long or ended too early. The values are Percentile range or Average Run Time (in percentage or by minutes). |
|
Defines the number of standard deviations of job run in this service. Percentile Range is the default method for specifying Job Run-Time Tolerance. |
|
The percentage of the time (based on the average run time for the job) or the number of minutes that the job can be early or late, and still be considered on time. |