By default, the server calculates anticipated end times and critical path using the average execution time of the last ten runs of the job regardless of execution-time differences of various runs (default profile). For more accurate average data, you can specify a job profile that considers the execution-time differences of a job for various days, times, or contexts. You can specify multiple profiles based on different criteria for a job.
For example, suppose that a job runs for one hour from Monday to Thursday and for six hours on Friday. If you do not specify a job profile, the server calculates anticipated end times and critical path based on the average execution time of the five runs of the job during the week. Using the default profile, the average execution time of the five runs is two hours, which is double the execution time for the job runs on Monday to Thursday and only one third of the execution time for the job runs on Friday. However, with job profiling, you can store job information for each run of the job based on a specified profile.
To override the default job profile, you associate a profile designation string for a given job. The profile string can be explicitly specified or calculated dynamically through JavaScript scripts and expressed using symbolic variables or the %VAR global variables function. For example, if a job execution profile uses the %APPL._SDAY symbolic variable as the profile string, the server calculates the job’s anticipated end time based on the day of the week the Application is scheduled. Assuming that this job is a part of an Application that is scheduled daily, when the Application runs on a Thursday, the anticipated end time for the given job is calculated based on the job’s Thursday runs and the elapsed time to execute this job is stored in the Thursday profile in the database.
You can override the job profile when you define the job or modify the job definition.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|