Support for R11.1 (AutoSys)

Support for R11.1 instances of AutoSys is included in . Note the following facts about R11.1 Support:

  • Supported instances: Automic Automation Intelligence supports R11.1 instances of AutoSys and pre-R11 instances within the same Automic Automation Intelligence server.

  • works with the R11.1 database schema: Specifically, all tables in R11 have an ujo_ prefix which is supported.

  • supports the custom job types: Each job in Automic Automation Intelligence will have an associated job type. This can be one of the standard job types such as box or command job as well as custom job_types. In the Automic Automation Intelligence job properties window, all jobs will display their job type and show the command and description that are inherited from the R11.1 job type.

  • Support for Ingres and Sybase database: In addition to SQL Server and Oracle, Ingres and Sybase are supported as a data source for an AutoSys database. At this time, we support Ingres or Sybase for the Automic Automation Intelligence database.

  • supports the Lookback dependencies: This feature of R11 allows conditions to be defined on a job along with a time interval. This type of dependency is understood and honored by the Automic Automation Intelligence prediction engine. For example, a condition in JobB s(jobA,8.30) specifies that JobB will run if jobA has succeeded in the past 8 hours and 30 minutes.

    In addition to the prediction engine, the root cause analysis feature also supports this type of dependency.

  • Dependencies are stored in the job_cond table only: To display dependencies in string format they will have to be created from the job_cond table. This translation will be done automatically.

  • Group/Application Support: In R11.1, jobs have a metadata attribute of group or application type. This allows separating jobs into various buckets. These categories will be displayed as properties in .

  • Machine Offline/Online: In R11.1, Automic Automation Intelligence will detect the offline status and display the job in not-run status. If the Target Job requires the job to complete, the jobstream status will be root cause 12 Machine is offline.