Cyclic

Indicates that the job/SMART folder must run at a designated time, interval of time. A non-cyclic job/SMART folder is a job/SMART folder, which if the scheduling criteria is satisfied, is ordered once by Control‑M on a given day (discounting reruns caused by a Rerun Job parameter or manual reruns). A cyclic job/SMART folder is rescheduled after execution for an additional possible execution. The job/SMART folder executes again only when the following circumstances occur:

The first run has completed.
The runtime schedule and execution parameters are still satisfied.
A specified number of minutes have elapsed since the last completion of the job/SMART folder, or the next specified runtime has been reached.
Jobs in the cyclic SMART folder, are automatically set to rerun according to the scheduled time set for the SMART folder

The cyclic job/SMART folder runs at the time designated according to the time or time intervals selected. The Run at and the Tolerance parameters can be set to enable a job/SMART folder to run after the specified time. If the job/SMART folder being executed runs over the proceeding job/SMART folder specified time, the proceeding job/SMART folder execution time window is extended to the number of minutes set in the Tolerance field. For example, if the Tolerance field is set to 15 minutes, the proceeding job/SMART folder can still be executed 0-15 minutes after the specified time. If the tolerance time interval has passed, the proceeding job/SMART folder will not be performed.

NOTE: The Run at option is relevant for one ODATE only. Specific times are sorted from each new day time to the next.

Additional information	Description

Usage	Optional
Format	Check box Selected – job/SMART folder is cyclic Clear – job/SMART folder is not cyclic
Alternate names	Control‑M/EM Utilities: CYCLIC Control-M Report: CYCLIC Control‑M/Server Utilities: -cyclic Control‑M for z/OS: Cyclic Control‑M/EM API: cyclic
Sub-parameters
Rerun Every	Fixed interval values to rerun a job/SMART folder: Minutes: 0-64,800 Hours: 0-1080 Days: 0-45
All intervals are from job's	Valid Values: End Start Target
Rerun using the following interval sequence	List of time intervals: Unit: Minutes, Hours, Days Amount:0-64,8000; 0-1080; 0-45
Run at	A list of specific times for the job/SMART folder to run. NOTE: This parameter supports time synonym.
Tolerance	Maximum delay in minutes permitted for a late submission when selecting a specific time (e.g. 5 minutes). Valid range: 0-999

Note the following:

Ordering a cyclic job/SMART folder as "non-cyclic": The %%CYCLIC variable can be used to override the Cyclic parameter for a job/SMART folder, or for all jobs in a folder. This variable is normally used when ordering a cyclic job/SMART folder for a single run.
NOTE: To indicate that all jobs/SMART folder ordered by the ctmorder utility (in Control‑M/Server) should run as non-cyclic jobs/SMART folder, include the following statement in the command line of the ctmorder utility: -variable %%CYCLIC N
Maximum number of days to wait for submission: The CYCLIC_MAXWAIT parameter for Control‑M/Server determines when cyclic jobs/SMART folder, which have executed at least once, should be removed from the Active Jobs database by the New Day procedure. Valid values are:
- KEEP – Jobs/SMART folder are removed from the Active Jobs database when Keep Active for days have passed regardless of whether the job/SMART folder ended OK. Default.
- NOT_KEEP – Jobs/SMART folder (non-cyclic and cyclic) are removed from the Active Jobs database at the next run of the New Day procedure. Cyclic jobs/SMART folder are not removed if they are executing when the New Day procedure begins. Instead, they are removed at the run of the following New Day procedure.
  For more information about Control‑M/Server parameters, see Control-M/Server parameters in Control‑M Administration.
Terminating a cyclic job/SMART folder: Special care should be taken when specifying a cyclic job/SMART folder. If not defined appropriately it may cause an endless loop in which the job/SMART folder is continually resubmitted for execution. If a cyclic job/SMART folder is executing when the New Day procedure is run, the job/SMART folder is changed to non-cyclic and an appropriate message is written to the Control‑M log. It is the user’s responsibility to review these messages and handle them accordingly.
You can prevent subsequent iterations of a cyclic job/SMART folder by using the Do Stop Cyclic parameter. If a cyclic job/SMART folder is terminated by a Stop Cyclic Run parameter, the View Details screen displayed by option Z in the ctmpsm utility contains Cyclic:T where T indicates "Terminated".
For z/OS jobs/SMART folder: Cyclic jobs/SMART folder cannot include a DO RERUN statement (Rerun Job).
- For cyclic folder: When a Cyclic SMART folder recycles (starts the next execution), the conditions between the jobs in the SMART folder are cleared (deleted) to maintain the jobs' original dependencies. Conditions that define dependencies between jobs in the SMART folder, which exist when the folder is recycled, are cleared to avoid parallel execution of the jobs in the SMART folder using these conditions.
  The following rules apply:
  - Only conditions that define a dependency between jobs in the SMART folder are cleared. A condition must be defined as an OUT condition of a job in the folder and as an IN condition of a job in the folder to be cleared.
  - Conditions are cleared even if there are jobs outside the SMART folder that depend on them. Conditions may impact jobs outside the SMART folder and still be cleared.
  - Conditions are not cleared if they are added using a DO action in the jobs.
  - Conditions are cleared just before the next cycle begins. Conditions remain after the SMART folder is complete and wait for the next cycle to start.
  - Conditions added by the SMART folder are not cleared.

Parent Topic

Scheduling Parameters