Script “sla” for daily batch has been created on all applicable Autosys instances (ASI, ASP, ASV) to manually Check our Batch and Online SLA goals.

 

When you run the script it will display the SLA (Service Level Agreement)  goals for that autosys instance.

 

For the ASI instance there are only 2 SLA goals:   BIS IB and BIS DATA.

 

Example: (ASI) autosys running the sla command will display the following results:

 

Sat Oct 15 00:33:38 CDT 2016

____________________________________________________________________________________

 

BIS IB - due complete by 05:00am CST - Wait for email from BIS Group before sending System Problem Email.

pioir_pfp_sla_mart_watchd                                        -----                10/14/2016 04:32:09  AC    

 

BIS Data - due complete by 09:00am CST.

pioir_infra_evtmon_loadd                                           ------                10/14/2016 04:41:18  AC  

 

____________________________________________________________________________________

Sat Oct 15 00:33:39 CDT 2016

 

The above 2 jobs are due complete by 5am and 9am.  Notice that both jobs are in AC “Activated status. They have not run yet. Ops should be monitoring the pioir batch cycle, and running reph.pl to determine when the average start time of the job is and jdep’ing back for its dependencies to verify the process batch flow is moving as expected. If not applicable action needs to be taken.

 

The 2nd job pioir_infra_evtmon_loadd  has a hard start time of 02:00am Daily

 

So ideally, we run the script to identify what is not in an “SU” status and check those batch or online jobs as needed.

 

Once the job is in success “SU” the sla goals have completed. Hopefully prior to the SLA goal. If this is beyond the SLA goal time we need to report it as applicable late with a system problem email.