Changes to Existing Features - 11.3.6 SP5 CUM1

This article details the changes to existing features in CA Workload Automation AE Release 11.3.6 SP5 CUM1.
wcc114sp5p
This article details the changes to existing features in CA Workload Automation AE Release 11.3.6 SP5 CUM1.
Priority is Honored for Jobs with Load Balancing and Resources Attributes
 
If you defined jobs with load balancing and resources attributes, jobs with highest priority run ahead of jobs with lower priority. If higher priority jobs are queued in the QUE_WAIT or RESWAIT state, then lower priority jobs are queued behind the higher priority jobs and remain queued until all higher priority jobs leave their queued states.
CA Workload Automation AE follows these rules to run jobs with priority, load balancing attributes, and resource attributes:
  • Jobs with the highest priority and load balancing attributes run ahead of jobs with lower priority for the same machine-based queue.
  • Jobs with the highest priority and resource attributes run ahead of jobs with lower priority for the same virtual resource-based queue.
  • Jobs with lower priority and load balancing attributes enter the QUE_WAIT state when higher priority jobs for the same machine-based queue are in the QUE_WAIT state.
  • Jobs with lower priority and resource attributes enter the RESWAIT state when higher priority jobs for the same virtual resource-based queue are in the RESWAIT state.
  • Jobs with equal or higher priority and load balancing attributes run if there is sufficient load on the machine to execute.
  • Jobs with equal or higher priority and resource attributes run if there are sufficient resource units to execute.
  • Jobs with equal or higher priority and both load balancing and resource attributes run if there is sufficient load on the machine and sufficient resource units to execute.
You can send a CHANGE_PRIORITY event to change the priority of RESWAIT jobs.