Changes to Existing Features - Release 11.3.6 SP2

This article details the changes to existing features in CA Workload Automation AE Release 11.3.6 SP2.
wcc114sp5p
This article details the changes to existing features in CA Workload Automation AE Release 11.3.6 SP2.
Documentation in the Product Image
The product documentation is no longer included in the product image. You can access the documentation online using this DocOps platform.
Retrieve Information of a Machine Using Web Services
Using web services, you can now retrieve information of a specific machine or multiple machines. For more information, see Manage Machines.
Calendar Name and Description
You can now use the autocal_asc utility to add or modify a description for a calendar. The description can be up to 1024 characters.
The calendar name can now contain up to 64 characters.
Updates to the ON_NOEXEC Feature
In the current release, the following changes are made for the ON_NOEXEC feature:
  • JOB_ON_NOEXEC event
    The scheduler processes the JOB_ON_NOEXEC event similar to that of the CHANGE_STATUS event to INACTIVE.
    For example, if you send the JOB_ON_NOEXEC event to a job in a box, the effect is the same as sending the CHANGE_STATUS event to INACTIVE for a job in a box. The scheduler sets the job to the ON_NOEXEC status and also sets the internal secondary status to INACTIVE, so that the scheduler evaluates the overall box status as if the job entered the INACTIVE status.
    To take the job off the ON_NOEXEC status, you must send the JOB_OFF_NOEXEC event. Sending manual CHANGE_STATUS event does not change the status of the job. To complete the NOEXEC job immediately so that the scheduler evaluates the job as if the job entered the SUCCESS status, send the FORCE_STARTJOB event.
  • JOB_OFF_NOEXEC event
    When the scheduler processes the JOB_OFF_NOEXEC event for a job, it places the job in the INACTIVE status. If the job is in a box, the scheduler evaluates the overall box status as the job is entering the INACTIVE 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 status.
  • Evaluation of downstream dependent jobs
    When you send the JOB_ON_NOEXEC event to a job, the effect is the same as if the job enters the INACTIVE status. The scheduler does not immediately schedule jobs that have a dependency on the NOEXEC job nor does it evaluate their success conditions to success. Instead, the scheduler evaluates the conditions of downstream dependent jobs as if the predecessor job is set to the INACTIVE status.
    When the job's starting conditions are met and the scheduler sends the BYPASS event, the effect is the same as if the job enters the SUCCESS status with an exit code of 0. The scheduler schedules jobs that have a dependency on the NOEXEC job and evaluates their success conditions to success.
Sending More Detailed Events to External Instances
When a local scheduler sends events to external instances, it populates the Event text field to indicate the action in the local instance that resulted in the external event. The event text can be as follows:
  • Job
    job name
    entered
    status