The total number of tasks in each day in the Workload Distribution Report includes jobs that were not removed at New Day (Held, Ended not OK, maxwait etc.). This is the reason why the same job appears twice in the list.
The following explains how tasks are being counted:
- The task count is based on the aggregated total number of jobs loaded into the Active Jobs database in Control-M within a 24-hour period.
This does not apply to customers who are licensed based on other units of measure such as MIPS, CPU, or tiers.
- A loaded task refers to all Control-M tasks that are monitored by Control-M across all of your environments.
This includes development, staging, QA, pre-production, test, and production environments.
- Loaded tasks are counted when they are submitted, regardless of whether they execute.
- A job that runs more than once during the day (with the same Order ID) is counted as one task.
- A single job that executes more than one script is counted as one task.
- Jobs that have time zone settings may remain in the Active Jobs database for more than one day, but are only counted once as a single task.
- Cyclic jobs are counted as single tasks, regardless of how many times they run.
- SMART folders/tables and sub-folders/tables, which contain scheduling definitions, and are listed as jobs in the Active Jobs database, are not counted as tasks.
- DUMMY jobs are counted as regular jobs.
Please note that when the checkbox "keep all jobs until folder is removed" on a SMART folder is selected,
This will mean that any job that stays in the AJF is counted for each day that it is there.
This also means that this can cause a usage alert if the daily amount is very close to the normal daily amount of jobs and the jobs in the retained / kept folder cause the jobcount to go over the configured threshold.