CA7 Exceeded SLA alerts received hours after Late Time for jobstreams with Generation Data Group Datasets

Products

• Automic Automation Intelligence

Issue/Introduction

CA7 Exceeded SLA alerts received hours after Late Time when a jobstream has a Dataset that is a Generational Data Group(GDG), which can cause a circular dependency in AAI.

 

For example, the job definition in the CA7 LJOB file shows the (0) after the data set name which identifies it as a GDG :

DSN=DISK.JOBABC02.JOBABC03.JOBABC04(0)                                                                                    
            DSNBR=DS00XXXXX  SCHID=000   VRSN=14078/0949                                                                            
            CREATED BY JOBABC02

 

This scenarios can introduce a circular dependency, which can prevent AAI from being able to make a prediction on the the Jobstream run.

 

When AAI cannot make a prediction on when the target job in a jobstream will complete, it will enter an Unknown status if there are no root causes identified. 

 

When a jobstream is in an Unknown status, no alerts will be generated until AAI can make a prediction on the target job's end time.

 

When the alerts are received late, usually you can track the time of the alert back to around the time the target job started or another job starts that runs after any circular dependencies, which allows AAI to make a prediction and generate alerts on that jobstream run.

 

Once the predictions are available and AAI sees the Late Time has been breached, it will generate the Exceeded SLA alert at that time.

 

Environment

Release : 6.4.2-2

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR CA 7

Cause

Defect DE538936

Resolution

Fix to break the circular dependency  on GDG's has been introduced in 6.4.5