ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

LASTRUN value is blank on forced-complete ESP job with non-zero EXECQT

book

Article ID: 237719

calendar_today

Updated On:

Products

ESP Workload Automation

Issue/Introduction

 

Job history:

FULLNAME        SCHED        START        EXEC     END          EXEC      EXEC FORCED

                DATE         DATE         START    DATE         END      QTIME COMPLETE

JOB008310      121221       121721       12.40.50 121721       12.41.05    14   YES

 

Note: Job ran for 14 seconds, and was forced to complete.  

When the ESP MAPGEN/JOBMAP job runs, it returns a blank value for 'LAST RUN:'  instead of the job's last execution date.

 

 

 

 

 

Environment

Release : 12.0

Component : ESP WORKLOAD AUTOMATION

Resolution

This is working as designed. 

The ESP application manager resets the JOBSTATS record flag for jobs that are force-completed, regardless of the job elapsed time (EXECQT). 

In other words, if the job ran, then was forced to complete, the job statistics would not be collected. 

This behavior was introduced in 2007.   If job statistic is collected for force-completed job, the average runtime will not be calculated correctly.

Job statistics is reported only for jobs that completed normally.  Abended jobs are skipped for job stats reporting.