Scheduling

Enables you to view all the calendar dates in a selected year of the selected rule-based calendar.

Determines which rule-based calendars are used that define when the SMART folder runs.

You can select a predefined rule-based calendar on the Control-M/Server or create a new one for this SMART folder, as described in Creating a SMART Folder Rule-Based Calendar.

Determines which rule-based calendars are used that define when the SMART folder does not run.

You can select a predefined rule-based calendar on the Control-M/Server or create a new one for this SMART folder, as described in Creating a SMART Folder Rule-Based Calendar.

Enables you to do the following:

• View and edit the details of a SMART folder rule-based calendar.

• View the details of a Control-M/Server rule-based calendar.

Determines the time frame when the SMART folder must execute.

Determines the earliest time that the SMART folder executes, as follows:

• No Start Time: Executes the SMART folder as soon as the prerequisitesThe part of the job definition that controls the flow of your jobs, such as an event that controls sequence or a resource that controls load are met.

• Select Time: Executes the SMART folder from the time that you define once the prerequisites are met.

  If the SMART folder remains in the Monitoring domain the next day, the SMART folder executes from the time that you define once the prerequisites are met.

Determines the latest time that the SMART folder executes, as follows:

• End of Day (New Day Time): The SMART folder waits until the end of the day for the prerequisitesThe part of the job definition that controls the flow of your jobs, such as an event that controls sequence or a resource that controls load to be met.

• Allow Submission Past Next New Day (>): The SMART folder waits indefinitely for the prerequisites to be met.

  If the SMART folder remains in the Monitoring domain the following day, it executes as soon as the prerequisites are met. It does not wait until the defined From time to execute.

• Select Time: The SMART folder waits until the time that you define for the prerequisites to be met.

  If the SMART folder remains in the Monitoring domain the following day, it waits to execute only until the defined time and when the prerequisites are met.

(z/OS Only) Defines the date and time when the SMART folder must finish executing. This includes the days offset.

Determines whether to schedule a folder as cyclicA folder or job that executes multiple times in one run, at a specific interval or specific times, or according to a specific sequence of intervals.

Determines the time interval between SMART folder executions, as follows:

• Interval: Defines a regular interval between SMART folder executions, in minutes, hours, or days, measured from the Start, End, or Target of the last execution of a SMART folder.

• Using Interval Sequence: Defines a sequence of varying intervals between SMART folder executions, in minutes, hours, or days, measured from the Start or End of the last execution of a SMART folder.

• At Specific Times: Determines a specific time of day for SMART folder execution, in hours and minutes, AM or PM.

Determines the number of minutes to supplement the rerun execution time if the current SMART folder execution overruns the time defined in At Specific Times.

If the time of day defined in At Specific Times plus the Tolerance time is overrun, the SMART folder waits for the next time defined in At Specific Times to execute, once the prerequisites are met.

On z/OS, you can add the days offset.

Determines the maximum number of reruns, as follows:

Rules:

• 0–99

• z/OS:

  • Cyclic Jobs: 0–9,999

  • Regular Jobs: 0–255

For more information, see Events.

Determines the time zone where the SMART folder is scheduled to run. For more information, see Time Zone.

(z/OS Only) Defines the name of the JCL member to use when the job automatically reruns.

Rules:

• Characters: 1–8

• Case Sensitive: Yes

• Invalid Characters: Blank spaces, non-English characters.

(z/OS Only) Defines the name of the Control-M periodic calendar where the job statistics are collected.

Rules:

• Characters: 1–8

• Case Sensitive: Yes

• Invalid Characters: Blank spaces, non-English characters.

Determines the number of additional days after the defined run date that the SMART folder remains active and awaits execution,

if it fails to execute at the originally defined time. Sub-folders and jobs in a SMART folder remain active according to the Keep Active value defined in the SMART folder.

• The job status for waiting jobs changes to Ended OK on the following day.

• All jobs are kept in the SMART folder until it is removed.

Valid Values:

• For: Keeps the SMART folder active, where it awaits execution for the number of extra days that you define, as follows:

  • 0: SMART folder executes only on the run date.

  • 1–98: SMART folder awaits execution for the number of extra days that you define.

• Forever: Keeps the SMART folder active, where it awaits execution indefinitely.

Determines whether to keep the jobs in the SMART folder until all of the jobs complete execution. They are then removed at the same predefined date as the SMART folder.

Enables you to specify a minimum period to keep the SMART folder in the Active Jobs database after the SMART folder is set to Not OK. This option is only available when you select the Keep All Jobs in Folder checkbox.

Defines the name of the SMART folder rule-based calendar.

Rules:

• Characters: 1–30

• Invalid Characters: * (asterisks), blank spaces.

Defines the scheduling of the SMART folder rule-based calendar as follows:

• Every Day: Runs the jobs in the SMART folder every day.

• None: Does not schedule the jobs, and only runs them manually, as described in Running Jobs or a Workspace.

• Specific Dates: Runs the jobs in the SMART folder on dates that you select.

• Free Space on PDS: (z/OS Only) Defines the name of a partitioned data set (PDS) that is checked for free space, as follows:

  • Partition Data Set: Defines the name of a partitioned data set to check for free space. If the partitioned data set has fewer than the minimum number of required free tracks (as defined in the Minimum Number of Tracks Parameter), the job is executed.
  • Minimum Number of Tracks: Defines the minimum number of free partitioned data set tracks required by the library that is specified for the Partition Data Set parameter.

• Advanced: Runs the jobs in the SMART folder according to weekdays and/or month days, and specific months using a rule-based calendar.

Defines the confirmation calendarA calendar that you use to confirm the days when jobs run, with a policy for non-working days that validates your scheduling dates, which can be any Regular or Periodic Calendars that are already published. Jobs in SMART folders that are scheduled on a specific day are checked against the confirmation calendar.

Determines one of the following policies to apply when a job that is scheduled to run is not in the confirmation calendar.

• Disable Run: Prevents the job from running.

• Run on Next Confirmed Day: Runs the job on the next day that is in the confirmation calendar.

• Run on Previous Confirmed Day: Runs the job on the previous day that is in the confirmation calendar.

• Run (Ignore Confirmation Calendar): Runs the job and ignores the confirmation calendar.

Determines the number of working days that Control-M can shift a job run. Depending on the shift value and the Exception Policy, the job runs on an earlier day, a later day, the original scheduling date, or never.

Valid Values:

• 0: Prevents the job from running.

• 1–99: Shifts the job to run the number of days that you specify, in either direction.

Enables you to view all the calendar dates in a selected year of the selected rule-based calendar.

Determines which parent rule-based calendars are used that define when the sub-folder runs, as follows:

• All Parent Calendars: The sub-folder runs on the dates defined in all the parent SMART folder rule-based calendars.

• Select from Parent: The sub-folder runs on the dates defined in the parent SMART folder rule-based calendars that you select.

Determines which Control-M/Server rule-based calendars are used that define when the sub-folder does not run.

Enables you to view the details of a rule-based calendar.

Determines the earliest time that the sub-folder can execute, as follows:

• No Start Time: Executes the sub-folder as soon as the prerequisitesThe part of the job definition that controls the flow of your jobs, such as an event that controls sequence or a resource that controls load are met.

• Select Time: Executes the sub-folder from the time that you define once the prerequisites are met.

  If the sub-folder remains in the Monitoring domain the next day, the sub-folder executes at the defined time once the prerequisites are met.

Determines the latest time that the sub-folder executes, as follows:

• End of Day (New Day Time): The sub-folder waits until the end of the day for the prerequisitesThe part of the job definition that controls the flow of your jobs, such as an event that controls sequence or a resource that controls load to be met.

• Allow Submission Past Next New Day: The sub-folder waits indefinitely for the prerequisites to be met.

  If the sub-folder folder remains in the Monitoring domain the following day, it executes as soon as the prerequisites are met. It does not wait until the defined From time to execute.

• Select Time: The sub-folder waits until the time that you define for the prerequisites to be met.

  If the sub-folder remains in the Monitoring domain the following day, it waits to execute only until the defined time and when the prerequisites are met.

Determines the time zone where the sub-folder is scheduled to run. For more information, see Time Zone.

(z/OS Only) Defines the date and time when the sub-folder must finish executing. This includes the days offset.

(z/OS Only) Defines the name of the JCL member to use when the sub-folder automatically reruns.

Rules:

• Characters: 1–8

• Case Sensitive: Yes

• Invalid Characters: Blank spaces, non-English characters.

(z/OS Only) Defines the name of the Control-M periodic calendar where the job statistics are collected.

Rules:

• Characters: 1–8

• Case Sensitive: Yes

• Invalid Characters: Blank spaces, non-English characters.

Determines the number of additional days after the defined run date that the sub-folder remains active and awaits execution,

if it fails to execute at the originally defined time. Jobs in a sub-folder remain active according to the Keep Active value defined in the sub-folder.

• T job status changes to Ended OK on the following day.

• All jobs are kept in the sub-folder until it is removed.

Valid Values:

• For: Keeps the sub-folder active, where it awaits execution for the number of extra days that you define, as follows:

  • 0: The sub-folder executes only on the run date.

  • 1–98: The sub-folder awaits execution for the number of extra days that you define.

• Forever: Keeps the sub-folder active, where it awaits execution indefinitely.

Determines the scheduling of the job, as follows:

• Every Day: Runs the job every day.

• None: Does not schedule the job and only runs it manually, as described in Running Jobs or a Workspace.

• Specific Dates: Runs the job on the dates you select.

• Free Space on PDS: (z/OS Only) Defines the name of a partitioned data set (PDS) to be checked for free space, as follows:

  • Partition Data Set: Defines the name of a partitioned data set to check for free space. If the Partition Data Set has fewer than the minimum number of required free tracks (as defined in the Minimum Number of Tracks Parameter), the job is executed.
  • Minimum Number of Tracks: Defines the minimum number of free partitioned data set tracks required by the library that is specified for the Partition Data Set parameter.

• Use Parent Schedule: Runs the job according to the scheduling criteria of the parent folder.

• Advanced: Runs the job on an advanced schedule, as follows:

  • Run on Week Days: Defines a weekday schedule.

  • Run on Month Days: Defines a schedule for the days of the month.

  • Use: Determines which parent rule-based calendars are used that define when the job runs.

  • Exclude: Determines which Control-M/Server rule-based calendars are used that define when the job does not run.

Enables you to view the dates when the folder, sub-folder, or job is scheduled to run.

Determines the time frame when the job must start running.

Determines the earliest time that the job can execute, as follows:

• No Start Time: Executes the job as soon as the prerequisitesThe part of the job definition that controls the flow of your jobs, such as an event that controls sequence or a resource that controls load are met.

• Select Time: Executes the job starting from the time that you define and when the prerequisites are met.

  If the job remains in the Monitoring domain the next day, the job executes from the defined time and when the prerequisites are met.

Determines the latest time that the job can execute as follows:

• End of Day (New Day Time): Executes the job as soon as the prerequisites are met, until the end of the day.

• Allow Submission Past Next New Day: Executes the job as soon as the prerequisites are met, until the end of the day.

  If the job remains in the Monitoring domain the next day, the job executes as soon as the prerequisites are met and does not wait for the defined From time.

• Select Time: Executes the job until the time that you define and when the prerequisites are met.

  If the job remains in the Monitoring domain the next day, the job executes until the defined time and when the prerequisites are met.

(z/OS Only) Defines the date and time when the job must finish executing. This includes the days offset.

Determines whether to schedule a job as cyclic.

Determines the time interval between job executions, as follows:

• Interval: Defines a regular interval between job executions, in minutes, hours, or days, measured from the Start, End, or Target of the last execution of a job.

• Using Interval Sequence: Defines a sequence of varying intervals between job executions, set in minutes, hours, or days, measured from the Start or End of the last execution of a job.

• At Specific Times: Determines a specific time of day for job execution, in hours and minutes, AM or PM.

In z/OS jobs, this area also defines Rerun Member.

For options and rules, see Events.

Determines the number of minutes to supplement the rerun execution time if the current job execution overruns the time defined in At Specific Times.

If the time of day defined in the At Specific Times option plus the Tolerance time is overrun, the job waits for the next At Specific Times to run when the prerequisites are met.

On z/OS, you can add the days offset.

Determines the maximum number of reruns as follows:

Rules:

• 0–99

• z/OS:

  • Cyclic Jobs: 0–9,999

  • Regular Jobs: 0–255

(z/OS Jobs) Defines the name of the JCL member to use when the job automatically reruns.

Rules:

• Characters: 1–8

• Case Sensitive: Yes

• Invalid Characters: Blank spaces, non-English characters.

Determines the time zone where the job is scheduled to run. For more information, see Time Zone.

Pauses the job from running for a period of time, without the need to change its job definitionThe set of parameters that defines what the job does, when it must run, its prerequisites to run, and post-processing actions for Control-M to perform after its completion (also called a job processing definition) or calendarA reusable job schedule that you can apply to many jobs, which enables you to perform schedule changes from a single location, as follows:

• Always: Does not restrict the job by an activity period.

• Active: Activates the job between the From and To dates that you define.

• Not Active: Deactivates the job between the From and To dates that you define.

(z/OS Only) Defines the name of the Control-M periodic calendar where the job statistics are collected.

Rules:

• Characters: 1–8

• Case Sensitive: Yes

• Invalid Characters: Blank spaces, non-English characters.

(z/OS only) Determines whether to adjust the logical date for the job that is converted from a scheduling product other than Control‑M.

Determines the number of additional days after the run date that a job can remain active, awaiting execution. Jobs remain active according to the value defined at job level.

For waiting jobs, the status changes to Ended OK on the next day.

Valid Values:

• For: Keeps the job active, where it awaits execution for the number of extra days that you define, as follows:

  • 0: Job executes only on the run date.

  • 1–98: Job awaits execution for the number of extra days that you define.

• Forever: Keeps the job active, where it awaits execution indefinitely.

Defines a confirmation calendar, which can be any Regular or Periodic Calendar that has already been published.

Determines one of the following policies to apply when a job that is scheduled to run is not in the confirmation calendar.

• Disable Run: Prevents the job from running.

• Run on Next Confirmed Day: Runs the job on the next day that is in the confirmation calendar.

• Run on Previous Confirmed Day: Runs the job on the previous day that is in the confirmation calendar.

• Run (Ignore Confirmation Calendar): Runs the job and ignores the confirmation calendar.