Skip navigation
All Places > CA Automic Community > CA Automic Workload Automation > Blog > 2019 > March
2019
29/3/2019: Updated Script now available in Knowledge Base Article
A bug in the routine calculating the next period turnaround of Schedule Objects causes multiple or no executions of jobs after the day light saving switch.
The bug has been introduced in the following service packs per release:
Automation.Engine 11.2.9 and 11.2.10
Automation.Engine 12.0.6 and 12.0.7
Automation.Engine 12.1.3 and 12.1.4
Automation.Engine 12.2.1 and 12.2.2
Systems running on an earlier service pack of the same release are *NOT* affected. e.g.: AE 12.0.3 = not affected; AE 11.2.9 = affected
Any JSCH object in any system, independent from the system's local time zone can be affected. A Schedule Object is affected in case it has a time zone object defined which refers to a time zone in which a daylight saving switch is defined. Schedules with no time zone defined will fall back to the client's time zone. Hence, all Schedules within a client which is set to such a time zone are affected.
Daylight saving switches occur on several dates from early March to mid April depending on the country. The country the system is physically located doesn't affect the vulnerability. It's the setup of the TZ Object in Automic Automation.Engine only, which determines if the bug will occur or not.
An overview of countries with DST switch and when they are due can be found here:
and here
A script has been created to identify affected JSCH objects. The script will also provide update statements (one per object) to fix the turnaround time, which will correct the situation.
In order to be able to import the objects, you need to have SQLVAR_INTERNAL set to YES in the UC_SYSTEM_SETTINGS.
The script needs to be run once a day as affected JSCH objects can be identified one day before the daylight saving switch only.
An e-mail address can be defined in the top of the script to have a notification sent out in case faulty JSCH objects are found.
In case the Script identifies affected JSCH Objects, please execute the provided 'update' statement to fix it.
The script will not perform the update statement automatically for safety reasons.
You can easily grab the entire report and strip the timestamp at the beginning of the lines using a text editor to execute all statements with the tool of your choice.
Please don't forget to perform a 'commit' at the end, in cases the database used requires it.
A Hotfix is available. Details of the Hotfix and the script can be found in this Knowledge Base Article 

License Key Checks Removed

The requirement for a License Key based on customer contracted entitlement was removed from the products in V12.2.2. 

This was for a number of reasons:

  • Multiple Customer requests
  • Customer survey feedback
  • Removal of a License Generation process which does not add any meaningful value for the customer or Broadcom
  • Removal of any risk of a customer outage due to a missing/expired license key 

 

Telemetry

Telemetry functionality was added into the solution in V12.2.2

This enables information about usage to be sent to the Broadcom organisation if the customer agrees.

On first login to Client 0, you will be asked to Activate your product. Telemetry can be found in the documentation here Telemetry

The Site ID requested is available in any support ticket communication.

 

No Personal information is collected that could identify components (Servers, Network addresses etc). 

The information is restricted to the following for AWA 

  • Number of Automation Engine / HA instances
  • Number of Active nodes (Technology nodes, Application nodes and Midrange nodes)
  • Number of job executions

 

The information is restricted to the following for CDA / ARA

  • Number of Automation Engine / HA instances
  • Number of Deployment Targets

 

The Information is restricted to the following for ASO

  • Number of Automation Engine / HA instances
  • Number of Orchestration Targets