Share:|

Are you using Workload Policies to help manage your environment?

 

Learn how to take advantage of this feature to better manage your jobs based on Control-M/Agent availability and your application owners' needs.

 

This is the link on YouTube for the recorded session:

 

Connect With Control-M: Managing Workload Policies - YouTube

 

Here is the Q&A for this webinar (Connect With Control-M: Managing Workload Policies)

 

________________________________________________________________

 

Q: As soon as the period for the workload policy has passed will those job run automatically or do we need to run them manually?

A:  The Jobs affected by a work load policy will continue to run as normally without needing manual intervention once a Policy is deactivated or its time for effect has  passed.

________________________________________________________________

 

Q: What happens if I change workload policy when things are running that meet the filter criteria?

A:  Jobs that are currently running when a policy is activated or takes effect will continue to run on the host. Jobs submitted once the policy is activated or take effect will follow the Policy.

________________________________________________________________

 

Q: Does mapping only apply for Agents connected to same CTM/Server?

A:  Jobs are defined to run on the Control-M/Server. To move jobs to an Agent on another Control-M/Server, it will be necessary to change the Job Definition.

________________________________________________________________

 

Q: I see we can activate/deactivate workload policy - can we create/delete/update workload policy outside of the GUI?

A:  The Workload Automation GUI client is the only way to Create, Delete, or Modify Policies.

________________________________________________________________

 

Q: When he says stopping all jobs - does he really mean stopping submission of new jobs? Do job already running keep running?

A: Jobs currently running will complete, until the Policy takes effect and new jobs will not run on the Control-M/Server or be submitted to the new Agent/Host. 

________________________________________________________________

 

Q: Can you not modify a policy after it’s created?

A:  Policies can be modified once they are created, but the name field cannot be changed.

________________________________________________________________

 

Q: Is there a way to change RUNNING JOBS or Quantitative Resources to "ZERO".  Lowest level available is 1.  If not, is there a RFE to provide for this?

A: Request for Enhancement QM002066509 has been opened for this scenario. Its inclusion in a future release or fix pack has not been announced.

________________________________________________________________

 

Q: Why can’t you set the Quantitative Resource to zero?

A: The suggested way to stop all jobs is to use the "Stop All Jobs" option of Workload Policies. Jobs have to meet all the defined filter criteria for the Policy to affect them.

________________________________________________________________

 

Q: Is it possible to export/import workload policies into different EM environment?

A:  It is possible to export Policies using the util utility. Usage for this is "util -mcs -export -type workload -file {path\file}. If the EM Server is on UNIX/Linux this command will have to be prefaced with "em"

________________________________________________________________

 

Q: Are Workload Policies a new v8/v9 feature? Or did it exist in v7 with a different name?

A:  Workload Policies were known as Workload Management in Control-M 7.0.00. This can be accessed in the Enterprise Manager Application from Tools > Workload Management.

________________________________________________________________

 

Q: The filter criteria uses OR or AND operator?

A:  The filter criteria uses an AND operator, so for a Policy to affect Jobs, all the filter criteria must be met.

________________________________________________________________

 

Q: If you are executing a policy to not run any jobs preparing for a maintenance window. How will this affect jobs that are running when you execute the workload policy?

A:  Jobs that are running on a Host will continue to execute until they finish. No new jobs that meet the filter criteria will be submitted once the Policy is activated.

________________________________________________________________

 

Q: So if I set up a policy to stop all job submissions on a control-m/server, critical jobs on this control-m/server would still be submitted?

A: Jobs that are marked as Critical in their definition will run regardless if they meet filter criteria for a job.

________________________________________________________________

 

Q: Can we use workload policies to stop the all the jobs during maintenance window, without shutting down the Control-M Server?

A:  The Control-M/Server does not have to be shut down for a Workload Policy to be able to stop or otherwise affect jobs.

________________________________________________________________

 

Q: So a workload policy addressing number of jobs executing works regardless if a job has a quantitative resource?

A: Number of Jobs and Quantitative Resource are separate categories so a Policy defined to affect one and not the other will not consider

________________________________________________________________

 

Q: Currently we are using the QR's for stopping the jobs on each agent during the outage window. For this we are using new jobs, which is consuming our license count. Can we replace these jobs with workload policy?

A: A "Number of Running Jobs" Workload Policy can be used for this purpose

________________________________________________________________

 

Q: Is it possible for Mass update in version 9?

A: Workload Policies must be updated one at a time in the GUI Client.

________________________________________________________________