A job definition contains job processing information, which defines what, where, and how a job runs. For example, the job might run a script on a particular computer. The following procedures describe some of the procedures that are used in the process:
Procedures |
Description |
---|---|
Enables you to define a job that includes the following types of parameters:
|
|
Enables you to define containers of one or more jobs, which enables you to organize your jobs according to schedules or resources. You can define as many folders as you need, and assign each folder to a specific Control-M/Server. For more information on the types of folders, see Folder parameters. |
|
Enables you to define containers of one or more jobs and Sub Folders, which enables you to organize your jobs according to schedules or resources. The jobs and Sub Folders in a SMART Folder (for non-z/OS jobs) can inherit definitions from parent SMART Folder. |
|
Enables you to define containers of one or more jobs and Sub Folders (for non-z/OS jobs), which enables you to organize your jobs according to schedules or resources. The Sub Folder can inherit definitions from the parent SMART folder. |
|
Enables you to create a calendar that you can apply to all jobs in your Control-M/Server. |
|
Enables you to define a job that is defined to rerun. |
To test your design, you can temporarily identify the job processing definitions as type “Dummy,” which executes the batch flow without actually running the jobs. For more information on Dummy jobs, see OS Dummy job parameters.
Parent Topic |