Usage Reporting Tool

The Control-M Usage Reporting Tool measures peak usage across all of your Control-M environments for license auditing and compliance purposes. The Usage Reporting Tool provides a wizard-based interface to assist you with generating usage reports showing your aggregated peak usage over the last year. The tool displays task usage, installed optional components such as the BMC Batch Impact Manager and Control-M Self Service add-ons, Control-M for Advanced File Transfer application plug-in, and Endpoint data.

If you want to connect the Usage Tool to Oracle RAC, see 000075660.

The Usage Tool counts tasks, which are based on the total number of jobs present in the Control–M Active Jobs databases within any 24-hour period, but does not apply to users whose license is based on other units of measurement, such as MIPS, CPU, or tiers. Tasks in the Control-M Active Jobs database refer to all Control-M tasks that are monitored by Control-M across all of your Distributed Systems or Mainframe environments, which includes development, staging, QA, pre-production, test, and production environments.

Tasks are counted according to the following rules:

• Regardless of whether they execute or not.
• A single task that executes more than one script is counted as one task.
• A task that runs more than once during the day (with the same Order ID) is counted as one task, which includes cyclic and tasks that are re-run.
• Tasks that have time zone settings may remain in the Active Jobs databases for up to three consecutive days, but are only counted once as a single task.
• Jobs that are ordered to run on a future date are counted every day the job resides in the Active Jobs database.
• SMART folders and sub-folders, which contain scheduling definitions, and are listed as tasks in the Active Jobs database, are not counted as tasks.