# © 2013 IBM Corporation Discover how to simulate and forecast the impact of changes on your workload environment How can you better satisfy Service Level.

## Presentation on theme: "© 2013 IBM Corporation Discover how to simulate and forecast the impact of changes on your workload environment How can you better satisfy Service Level."— Presentation transcript:

© 2013 IBM Corporation The Challenge Critical jobs have deadlines that have to be met. If a deadline is at risk it is important to know this in advance to take recovery actions. Business users are asking when a specific processing will complete A combination of an accurate job duration estimation algorithm and the critical path is the solution.

© 2013 IBM Corporation An accurate job duration prediction is fundamental to estimated the end time of a critical job. Job duration in seconds will reduce the error in case of many jobs with a short duration. The foundations of this solutions are: Improve the measurement of start time and end time of a job Improve the prediction algorithm The Solution

© 2013 IBM Corporation Dates and JOB duration in seconds

© 2013 IBM Corporation Start time and End time are now showing the seconds. Job duration is calculated in seconds. Minimun duration is calculated in seconds. Job duration statistics are using seconds Dates with seconds

© 2013 IBM Corporation Built in JOB duration prediction algorithms

© 2013 IBM Corporation Detailed statistics are reported for common periods Global statistics for all the job instances Weekly statistics Monthly statistics Monthly (from the end of the month) statistics Run cycle statistics An algorithm identifies the period (if present). A linear prediction algorithm is used to analyze the samples of the period. A confidence interval is showing the variance of the samples for the identified period This is the default prediction algorithm for all the jobs. Built in job duration prediction algorithms

© 2013 IBM Corporation IBM SPSS Statistics is a well known software package used for statistical analysis. It is using the whole job history to identify patterns and make the right prediction. It is not using a pre-defined list of possible periods. It Is using sophisticated algorithms. This processing is being used for a subset of jobs identified by the user. A confidence interval is provided SPSS for advanced job duration predictions

What if IBM Workload Scheduler What If Analisys on critical jobs using a Gantt view WHAT is involved IF a server is broken and needs 3 hours to repair? WHAT happens to my plan IF my SAP server stops for maintenance? WHAT will I risk IF the file I'm waiting for is late?

Variable Duration and Deadline The accuracy of job durations and deadlines is very important to leverage some TWSz functionalities, such as workload planning calculations or the alerting and handling of the Critical Jobs. Many customers have jobs whose durations and deadlines change on certain dates. The new variable duration and variable deadline feature allows customers to specify different durations and deadlines for the same job, by associating them with internal or external run cycles.

Automatic cleanup of abended instances

© 2013 IBM Corporation The Challenge Pre-Production Plan (LTP) is stored on DB and automatically cleaned up Cleanup process does not remove instances after the First Not Completed Job Stream instances Large Pre-Production Plans can have bad performance impacts Job Streams left in ABEND are causing Symphony and Pre-Production plan growth and then performance degradation Current Solution: manually cleanup ABENDed job streams

© 2013 IBM Corporation The Solution: Until days With next TWSd version we are adding a new option untilDays (ud) in optman This option sets a default until to every job stream instance, n days after its scheduled time An ABENDed job stream instance is then removed from the plan after n days The user can override this setting, using a specific until on the job stream definition Setting untilDays=0, no default until is applied Using this option, Administrator don't need to worry about cleanup of job stream instances