Changes to Existing Features - 11.3.6 SP5

This article details the changes to existing features in CA Workload Automation AE Release 11.3.6 SP5.
wcc114sp5p
This article details the changes to existing features in CA Workload Automation AE Release 11.3.6 SP5.
Support Global Resources for Box Job
You can now specify only global resources on a box job. However, the resource specified for a box applies only to the box and not to the jobs within the box.
Updated watch_no_change Attribute
You can now specify the watch_no_change attribute value in seconds, minutes, hours, or days. For more information about the watch_no_change attribute, see watch_no_change Attribute -- Specify the Time the File Must Remain Unchanged.
Change the Status of the Job that is in the ON_NOEXEC Status
You can now issue the following events to change the status of a job that is in the ON_NOEXEC status:
  • The CHANGE_STATUS event to change the status of a job that is in the ON_NOEXEC status to either the INACTIVE or SUCCESS status while remaining in the non-execution mode. When you change the status of a non-execution job to SUCCESS, the scheduler completes the job’s run and schedules the downstream dependent jobs. Changing the status of a non-execution box job to INACTIVE also changes the status of all the jobs in that box job to INACTIVE in non-execution mode. Changing the status of a non-execution box job to the RUNNING status starts the box job.
  • THE JOB_ON_NOEXEC event to an ACTIVATED job that is within a running box. The job remains in the ACTIVATED state in non-execution mode until its starting conditions are met. After the starting conditions of the job is met, the scheduler sends a BYPASS event and the job goes to the SUCCESS state in non-execution mode.
  • The JOB_OFF_NOEXEC event for a job. It places the job in the INACTIVE, ACTIVATED, or SUCCESS status based on the job’s existing status while in non-execution mode. If the job is in a box, the scheduler does not evaluate the overall box status. If you send the JOB_OFF_NOEXEC event to a box, all jobs in the box (including all jobs contained in lower level boxes within the box) are reset to the INACTIVE, ACTIVATED, or SUCCESS status.
KILLJOB Send Signal Behavior
On UNIX agents (r11.3, Release 11.3.5, or Release 11.3.6), you can now send multiple signals by entering a comma-delimited list as the value for the signal_num variable. The agent sends the first signal, sleeps for a second, sends the next signal, and so on.
In the previous releases, only the legacy agents supported this behavior.
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 run ahead of jobs with lower priority.
  • Jobs with lower priority and load balancing attributes enter a queued state when higher priority jobs for the same queue are in the RESWAIT or QUE_WAIT state.
  • Jobs with lower priority and resource attributes enter a queued state when higher priority jobs for the same queue are in the RESWAIT or QUE_WAIT state.
  • Job