The following table describes the General parameters for a z/OS job.
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. Value: Dummy (z/OS) |
|
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 the name of the 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. |
|
Parent Folder |
Defines the name of the folder that contains the job or Sub Folder. Names of folders and Sub Folders may be up to 64 characters, with the exception of Control-M for z/OS folders which may be up to 8 characters. Folder names cannot contain the character “/”. SMART Folders in Control-M for z/OS can only contain jobs (not Sub Folders). Read-only field |
More |
Defines an area of the Properties pane to click to define more parameters. |
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 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 node in the JES network where the job executes. |
|
Performs data set cleanup before the original job run. |
|
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. |
|
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. You can add a variable, as described in Adding a variable. |
|
Documentation |
Defines a description related to the job, and is saved in a defined location. The Documentation area in the Properties pane includes information about where to find the Documentation. In a z/OS job, the Documentation is in a Doc Member located in a Doc Library. In a non-z/OS job, the Documentation depends on whether the type is File or URL. For a file, the description is located in a file located in a file path. For a URL, the Documentation is located in a URL address. |
Defines the name of the library where the Documentation (description) is saved. |
|
Defines the name of the member where the job Documentation (description) is saved. |
|
Determines the order of job processing by Control-M in the Active Jobs database. |
|
Determines whether the z/OS job is an Emergency job. |
Parent Topic |