Pre-Con Ed: Critical Path Analysis with CA Workload Automation (AE) iDash - Overview

World®
’16
Critical Path Analysis with CA Workload
Automation (AE) iDash - Overview
Karen Cleever /CA Technologies/Sr. Principal Consultant
MFX12E
MAINFRAME AND WORKLOAD AUTOMATION

2 © 2016 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD
© 2016 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.
The content provided in this CA World 2016 presentation is intended for informational purposes only and does not form any type of
warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.
For Informational Purposes Only
Terms of this Presentation

Abstract
This presentation will give attendees an overview of using CA Workload Automation (AE) iDash
for analyzing Critical Path in your AutoSys environment. The session will target using iDash to
monitor critical path real time and analyze past runs using historical data.
Karen
Cleever
CA Technologies
Sr. Principal Consultant

Agenda
WHAT IS CRITICAL PATH ?
CRITICAL PATH VS ALL JOBS
QUESTIONS AND ANSWERS
HOW DO AUTOSYS EVENTS IMPACT CRITICAL PATH
MONITORING USING CRITICAL PATH
USING HISTORICAL DATA TO OPTIMIZE JOB FLOWS
1
2
3
4
5
6

What is Critical Path?
§ the sequence of stages determining the minimum time
needed for an operation, especially when analyzed on a
computer for a large organization.
OR
§ Longest sequence of activities in a project plan which must be
completed on time for the project to complete on due date.
An activity on the critical path cannot be started until its
predecessor activity is complete; if it is delayed for a day, the
entire project will be delayed for a day unless the activity
following the delayed activity is completed a day earlier.

Critical Path vs Critical Job List
§ The critical job list comprises jobs that must run successfully
for the SLA job to start or end successfully. The critical job list
is built for each SLA job by analyzing the job definition and the
dependency structure.

Critical Job List
JobE
Job DJobC
JobB
JobA
JobE
Job DJobC
JobB
JobA

Critical Path in iDash
§ iDash dynamically generates the critical path of each SLA. The
following items for each job in the critical job list are
evaluated:
– Status
– Average duration
– Date and time conditions
– Date and time parameters (such as run window and exclude calendar)

Critical Path vs Critical Job List
§ The jobs in the critical path represent the longest path to a
successful execution of the SLA job. The longest path is the
path that is predicted to take the most time to complete.
JobA
10 minutes
JobC
10 minutes
JobD 5
minutes
JobB
20 minutes
JobE
10 minutes

How Do Autosys Events Impact Critical Path
§ Jobs with FAILURE or TERMINATED status are evaluated with
these assumptions:
§ The jobs are assumed to restart promptly per the job
definition or by the operator.
§ The jobs are assumed to run for their average duration.
§ CA Workload Automation AE jobs are predicted to complete
with a status of SUCCESS.

§ Jobs running shorter or longer than their average run time
have the following impact:
§ Jobs running shorter than average decrease the remaining
processing time.
§ Jobs running longer than average increase the remaining
processing time
§ CA Workload Automation iDash adjusts the critical path to the
jobs with longer remaining processing time.

§ Jobs achieving ON_ICE and ON_NOEXEC statuses decrease the
processing time remaining.
Note: ON_HOLD job are presumed to remain on hold. When a
critical path job is put on hold, the SLA status becomes
PREDICTED MISS.

NPTF: Display problematic jobs on SLA detail
§ Exception Type that tells why the particular job is
problematic.
– Unsuccessful run - Unsuccessful AutoSys runs will display with a status
of Failure or Terminated; unsuccessful CA 7 jobs will display with a
status of Failed, Abended, Submit_Failed, or Canceled.
– Shorter than average - When the job ran for 10% less than its actual
average runtime and the difference of the duration of the last run and
the job’s average runtime is greater than 120 seconds.
– Longer than average - When the job ran for 10% greater than its actual
average runtime and the difference of the duration of the last run and
the job’s average runtime is greater than 120 seconds.
(NEW in 12.0.2)

Problematic Jobs

Why did this SLA Miss

When a Job Fails
§ Lets walk thru an SLA where a job fails.
§ Correct the failure

Using Reports
§ cp.report from CLI

Release 12.0.02 Features
Reporting
••Support hourly intervals on all reports
••Average run time to Job Run reports
••Filter jobs based on start/end times on AE/CA7 Job Run reports
••Application/Group fields on AE Job Status & Job Run reports
••Filter based on Job Types on Job Run & Job Status reports
••Filter jobs based on last X job runs
Security
••Manage SLAs based on EEM resource class (idash-sla)
••EEM Security enforcement: Create/update tags (idash-tag resource class), for Tags displayed on the Dashboard
••EEM Security enforcement: create/download/execute reports (idash-report resource class)
••Dynamic User Group based authorization
••Support for EEM authorization on CA7 Jobs
Monitoring
••Proactive Alerting: SLAs moved to Predicted Miss if jobs in SLA flow fail (prior to being part of Critical path)
••Track Problematic Jobs with every SLA run
••Displaying datasets in the Flow View for CA 7 Jobs
••Flow View enhancements Negative dependency handling, progressive loading support for large flows

Questions?

Thank you.
Stay connected at communities.ca.com

Pre-Con Ed: Critical Path Analysis with CA Workload Automation (AE) iDash - Overview

More Related Content

What's hot

Viewers also liked

Similar to Pre-Con Ed: Critical Path Analysis with CA Workload Automation (AE) iDash - Overview

More from CA Technologies

Recently uploaded

Pre-Con Ed: Critical Path Analysis with CA Workload Automation (AE) iDash - Overview