You can organize batch flows into the following hierarchies:
Application => Sub Application = > Folder => Job: Your site may have many different applications, such as Payroll, Accounting, Inventory, Customer Service. Each application has many jobs, and the jobs within an application may be further divided into Sub Applications. For example, the jobs in the Accounting application may be divided into Sub Applications such as Receivables, Expenditures, Government Reporting, etc. This hierarchy reflects how your site’s jobs are organized according to Application.
Control-M => Folder => Job: Each application, (for example, the Accounting application) may have jobs that run daily, other jobs that run weekly or monthly, and still others that run once per year. Frequently, jobs that run together are interdependent. One job may need to complete before another job can run. They also generally run on the same Control-M. For this reason, you organize jobs that are generally scheduled together into a logical grouping called a Folder, with the Folder running on a particular Control-M.
When you view jobs in Control-M, View tab, you can select different types of views according to Application, Sub Application, Folder and Jobs.
Control-M’s Workload Policy Management and Host Group Management features help you to better control, manage and balance the workload on Control-M resources and hosts. This is done in three primary areas:
Limiting resources available to groups of jobs in the active environment
Routing groups of jobs to execute on specific resources
Defining a resource’s availability in the dynamic environment according to specific times
