What's New In Automic Automation Intelligence 6.3.0

This section provides information about the new features and enhancements, bug fixes, and database changes that have been implemented in version 6.3.0:

Enhancements

CA Workload Automation ESP Support

Automic Automation Intelligence 6.3.0 is the first version that supports CA Workload Automation ESP (ESP).

Automic Automation Intelligence 6.3.0 in conjunction with the newly released ESP adapter allows customers to utilize ESP on the mainframe to include their ESP instances as part of their automation engine landscape. Both historical and predictive analytics are now available for ESP instances.

For more information, see:

Important! Before installing the ESP Connector, make sure that all the necessary CA Workload Automation ESP components are installed and configured.For more information, see:LINKS HERE

Jobstream Run Status

In previous versions, when the target job of the jobstream was a container and the container run completed with a non-success status, the status of the jobstream was Complete.

With this version, the status of the jobstream in these cases is Unknown.

Universal Schedulers

Automic Automation Intelligence 6.3.0 contains the following improvements for Universal schedulers:

  • Improved support in the Termination Status Report.

  • Universal Connectors: All the scripts that are required to generate a client certificate are now added to the connectors directory ino the root level of the AAI installation

  • Option to install multiple universal connectors through rpm on a single server

  • Option to configure the job definition download to occur at one or more selected times per day rather than entering a duration-based interval

  • Ability to send in multiple caused by (predecessor) information with subsequent events for a particular job run. This new function provides the following benefits:

    • More accurate predictions

    • Jobstream run wiring based on multiple job runs impacting a downstream job run

  • Condition type enhancements:

    • Support for the DATES_WITH_RECURRING_TIMES condition type

    • numAllowedOverlappingRuns field added to the FIRM_DATES_WITH_TIME condition type in the POST /conditions API

    These enhancements allow support of recurring or cyclic job conditions.

  • As of this version, AAI supports, displays and calculates the latency for start to start job dependencies. For more information, see Job Dependencies in Universal Schedulers.

Encrypted Information

The confidential configuration information available in the JobScheduler table in the AAI database schema is now encrypted.

Finish to Start Delay Column

With this version,the Finish-Start column in the Jobstream Summary and Jobstream Detail reports is available for all scheduler types, including Universal schedulers

AdoptOpenJDK

This version supports AdoptOpenJDK.

Garbage Collection

The default JVM settings have been modified to use the G1 garbage collector. The AAI application has been changed to allow the JVM to control when full garbage collection is performed.

Application Landscape Feature Removed

The preview of the Application Landscape feature which was released in early 2020 has been removed from this release. We received valuable feedback from the user community as a result of the preview of this functionality and will be incorporating that feedback into future releases.

Bug Fixes

These are the bugs fixed for Automic Automation Intelligence 6.3.0:

General

  • Removed an UnsupportedOperationException that occurred in the ForecastDriver when a combination of older and newer scheduler types were included in a single AAI environment

  • Resolved security vulnerabilities

    Resolved by upgrading spring-framework 4.3.26

    • CVE-2018-1270

    • CVE-2018-1275

    • CVE-2018-15756

    • CVE-2018-1272

    • CVE-2018-1257

    • CVE-2018-11039

    • CVE-2018-11040

    • CVE-2018-1271

    • CVE-2018-1199

    Resolved by upgrading Spring Boot 1.5.22

    • BDSA-2018-1076

    • CVE-2018-1196

    Resolved by upgrading c3p0:JDBC DataSources/Resource Pools 0.9.5.5

    • BDSA-2018-4478

    • CVE-2019-5427

    Connector framework: Resolved by upgrading net.minidev:json-smart to 2.4.2

    • CVE-2021-27568

AutoSys Next Generation

  • Resolved an issue with the Termination Status Report that prevented the statuses that should be included in the report from being available for selection

  • Improved job run linkages to properly link restarted job runs due to job failures into the proper jobstream run

  • Fixed an IllegalArgumentException that occurred when a job failed and then was FORCE_STARTED

Universal Schedulers

  • Fixed an IllegalArgumentException that occurred when Universal job properties were selected from the Columns tab for a Termination Status report

  • Fixed an issue where a user-defined New Predicted Duration for a jobstream run was not correctly reflected in the predicted end time

  • Improved the Universal Jammer so that different events with the same timestamp sent in different transactions from the connector do not result in missed events in AAI

Control-M

Date and Time Processing Failures

Multiple calendar, date, and time processing errors have been fixed. These issues prevented job start time predictions.

  • A missing calendar error occurred due to bad or incomplete smart table data.

  • There was an issue processing previous and next working day schedules for day-of-week and day-of-month calendars.

  • Data center’s daylight savings start and stop times were being incorrectly parsed.

Job/Event Publication Failures

Issues preventing jobs and events from being published to AAI have been fixed.

  • There was an issue when logging job details during error processing.

  • Job publication would fail when jobs had empty or missing job names.

  • The connector was failing to publish events for repeating Control-M Jobs.

  • Event publication was failing due to invalid processing of ‘runinfo_history’ data and causing a circular dependency.

Database Schema Upgrade Summary from 6.2.0-2

Modified Tables

 

Table Name Change Type Column(s) Affected
JobStatisticsModel Rename schedId to jobRunContextId
JobCondition Rename schId to jobRunContextId
JobCondition Rename triggerSchId to dependentJobRunContextId
RecommendedStartTime Rename schId to jobRunContextId
JobRun Rename schId to jobRunContextId
JobStream Rename schId to jobRunContextId
JobStream_StartJob Rename schId to jobRunContextId
JobStatisticsModel Modify jobRunContextId*
JobCondition Modify jobRunContextId*
JobCondition Modify dependentJobRunContextId*
RecommendedStartTime Modify jobRunContextId*
JobRun Modify jobRunContextId*
JobStream Modify jobRunContextId*
JobStream_StartJob Modify jobRunContextId*
JobRun Add activatedTime*
JobCondition Add numAllowedOverlappingRuns
JobCondition Add recurringFirstDateStartTime
JobCondition Add recurringFirstRunStrategy
JobCondition Add recurringSubsequentRunStrategy
JobCondition Add recurringMaxRepsPerTimeWindow
JobCondition Modify jobConditionType**

* column length increased to 21

** column length increased to 41

Dropped Tables

  • UIViewWidget

  • UIView

  • UIWidget

  • UIWidgetType

Automic Automation Intelligence Report Server Updates

An issue that produced a blank screen when relative dates were used with the Daily Batch Cycle Report in Insight has been fixed.

Connector Framework Updates

With this version, the rpm can be installed on any architecture (noarch).

Connector Updates

Automic Connector

  • The Automic Automation REST API password entry on the Add/Edit Scheduler panel has been modified to allow empty passwords.

  • A new function in the Add/Edit Scheduler pane prompts the user for the Automic System Name. With this enhancement, the Connection field in the Automic Automation system is automatically populated when launched through a URL from the Job Details of Gantt view for a jobstream run in the AAI client.

Control-M

Duplicate Calendar Name Support

From this version onward, AAI supports processing calendars with duplicate names across different data centers.

IWS

  • This version now prevents the StackOverflowError that occurred while analyzing a nested IWS job condition during NPTF Root Cause Analysis.

  • The connector event processing has been improved so that duplicate event records in successive event files from the IWSz mainframe are discarded and not sent to the Automic Automation Intelligence application.