search cancel

Validadity of Estimated End Time column during job running

book

Article ID: 190785

calendar_today

Updated On:

Products

CA Workload Automation iXP

Issue/Introduction

Can a description of the accuracy , use and general information about this display column be shared  and it's intended use.  Test shows that it blocks with 5 minute intervals and there is no job count run amount that "synchronizes" the history.  For example average of 10 runs will give more valid information.

Environment

Release : 11.3

Component : CA WORKLOAD AUTOMATION AE IXP

Resolution

The Estimate End Time is calculated based on the job's START TIME + the job's AVG_RUN_TIME.
A job's Average Run Time is calculated by DBMaint based on the job's past job run history.

Ref: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/intelligent-automation/workload-automation-ae-and-workload-control-center/11-3-6-SP8/reference/ae-job-information-language/jil-job-definitions/avg-runtime-attribute-define-average-run-time-for-a-new-job.html

Note: When the DBMaint script runs, it recalculates the average run time for each job in the database.

When a job is defined and if avg_runtime is not specified, there is no record for the job in ujo_avg_job_runs and 5 minutes is used as the estimated run time.
Therefore the more runs the job has, the better the average run time.

The AVG_RUN_TIME can also be update via a JIL command like the folloiwng:

jil
jil> update_job:
jil> avg_runtime:
jil> exit

The avg_run_time is stored in table UJO_AVG_JOB_RUNS.