Workload Policies

Workload Policies enable you to manage and balance resources and hosts for multiple jobs within or across Workspaces.

The Workload Policies Definitions tool enables you to apply and schedule Resource Pools, define job restrictions, and map hosts to a group of jobs that share similar Control-M/Servers, Applications, Sub-applications, folders, job types, or hosts. If multiple active Workload Policies are defined, you can prioritize the order that they run in. These tools eliminate the need to individually redefine, reschedule, and reroute multiple jobs.

Once a week, bike rental data for hundreds of stations in multiple cities is retrieved, processed, and analyzed on 20 Agents, which are equally distributed in two locations, San Francisco and Seattle. Both locations usually have enough extra Agents available in case the machines in one location are unavailable. Based on this example, you can configure Workload Policies as follows:

  • Host Mapping: Due to a major storm, all of the Seattle Agents are down. To process the data, a Workload Policy is created to map, or reroute, the 10 Seattle Agent data analytics jobs to an additional 10 available machines in San Francisco.

  • Running Jobs Restrictions: The bike rental company isn't the only one who needs more Agents in San Francisco this week, so there aren't any extras available when the Seattle Agents are down. To deal with this restriction on available Agents, a Workload Policy is created restricting the number of running jobs to 10 at a time, instead of the usual 20.

  • Scheduled Resource Pools: The database used by the bike rental company can handle a maximum of 20 concurrent logins. However, the bike rental company now wants to regularly run 5 data visualization jobs, in addition to the 20 weekly data analytics jobs. Since all 25 jobs are set to run at the same time, and the database cannot handle more than 20 logins simultaneously, a Workload Policy Resource Pool is set to allow a maximum of 20 logins to the database on the day all the jobs run. This holds the extra 5 jobs from running that day until the resources are available.

The Workload Policies Monitor tool enables you to review the status of jobs grouped into Workload Policies.

  • You can assign a maximum of 20 Workload Policies to a job.

  • Critical jobs bypass Workload Policy rules that limit Lock Resources, as described in Lock Resources.

Creating Workload Policies Definitions

This procedure describes how to create Workload Policies Definitions. This enables you to group jobs with shared characteristics, or filters, and define Resource Pools, job restrictions, and host mapping.

Begin

  1. From the Tools drop-down list, select Workload Policies Definitions.

    The Workload Policies Definitions Workspace appears.

  2. From the Workload Policies Definitions Workspace toolbar, select New.

    The Workload Policies Definitions Details pane appears on the right.

  3. Do the following:

    1. In the Name field, type a name for the Workload Policy.

    2. In the Description, describe the purpose of the Workload Policy.

  4. In the Status attribute, select one of the following:

    • Active

    • Inactive

  5. From the Filter field, type or select any of the following shared characteristics, or filters, where your jobs are grouped in the Workload Policy:

    • Job Name or Member Name

    • Server

    • Application

    • Sub Application

    • Folder

    • Job Type

    • Host or Host Group

    For a list of available filter wildcards, see Pattern-Matching Strings.

  6. Define one or more of the following:

  7. Click Save.

    A confirmation message appears. The Workload Policy definition is now saved in the Control-M/EM.

  8. For a Workload Policy on a z/OS system, ensure that you have sufficient authorizations via the CTWSE02 security module. See Workload Policy Management Security in the INCONTROL documentation.

Defining Resource Pools

This procedure describes how to define Resource Pools in Workload Policies Definitions, which creates Resource Pools for a group of associated jobs for a defined period.

Begin

  1. From Resource Pools, click .

    The Resource Pool - Period Definition dialog box appears on the right.

  2. Define the Resource Pools for the jobs in the Workload Policy, as described in Resource Pools.

  3. From the Date Types drop-down list, select one of the following options to determine when the Resource Pools are enforced in the Workload Policy:

    • All Days

    • Every (Periodic Day of the Week)

    • Between (Specific Days in the Calendar)

    • Between (Specific Date and Time)

    • Every Week Between (Day of Week and Times)

    • On (Specific Days in the Calendar)

  4. From the Time field, select one of the following time options:

    • All Hours: Restrictions are enforced for all hours on the selected dates.

    • Between: Restrictions are enforced for a period that you define on the selected dates.

  5. Select Add.

    The scheduled Resource Pools appears under Resource Pools.

Defining Running Jobs

This procedure describes how to define Running Jobs in Workload Policies Definitions, which limits the number of concurrently running jobs for a defined period.

Begin

  1. From Running Jobs, click .

    The Number of Running Jobs - Period Definition dialog box appears on the right.

  2. From the Server drop-down list, select the Control-M/Server where the restrictions on the number of running jobs are applied.

  3. In the Running Jobs field, determine the maximum number of concurrently running jobs.

  4. From the Date Types drop-down list, select one of the following options to determine when the maximum number of concurrently running jobs is enforced in the Workload Policy:

    • All Days

    • Every (periodic day of the week)

    • Between (specific days in the calendar)

    • Between (specific date and time)

    • Every Week Between (day of week and times)

    • On (specific days in the calendar)

  5. From the Time field, select one of the following time options:

    • All Hours: Restrictions are enforced for all hours on the selected dates.

    • Between: Restrictions are enforced for a period that you define on the selected dates.

  6. Select Add.

    The scheduled running jobs restrictions appears under Running Jobs.

Defining Host Mapping

This procedure describes how to define Host Mapping in Workload Policies Definitions, which routes a group of associated jobs to a new host, or Agent.

Begin

  1. From Host Mapping, click .

  2. From the Control-M Server drop-down list, select the Control-M/Server where the required Host Groups are located.

  3. From the Host/Host Groups drop-down list, select the host or host group where the jobs are currently defined.

  4. From the Map To drop-down list, select the host or host group that you want the jobs to run on.

    The mapped hosts appear under Host Mapping.

Workload Policies Monitor

The Workload Policies Monitor enables you to review the status of jobs grouped into Workload Policies.

The Active Jobs panel displays the status of all active jobs across all Control-M/Servers, and not just the jobs defined in Workload Policies.

The following table describes the status columns that appear by default in the Workload Policies Monitor:

Column Name

Description

Name

Displays the Workload Policy name.

Wait Hosts

Displays the number of jobs in the Workload Policy that are waiting for host, or Agent, resources, due to one of the following reasons:

  • An Agent is unavailable.

  • An Agent is already running its maximum number of jobs.

  • An Agent is currently at its maximum CPU usage restriction level.

Wait Workloads

Displays the number of jobs that are currently waiting because of defined Workload Policy restrictions.

Running Jobs

Displays the number of concurrently running jobs.

Additional columns can be added by clicking , on the top left corner of the right pane.