One of my JOB taking so much Elapsed time compared to CPU time.
Example - CPU TIME = 10 MIN but ELAPSED TIME = 120 min in one of our JOB.
(Job contains COBOL,Eazytrive program. Database used - DB2,IMS and flat file are used in this JOB) 1)What could be the possible reason?
2)Is there any option availabe to reduce elapsed time?
3)What are all the loop holes for this reason(more elapse)?
Joined: 06 Jun 2008 Posts: 8165 Location: East Dubuque, Illinois, USA
For an active system, your ratio doesn't seem unusual -- I looked at one of our jobs that ran yesterday during month-end processing and it used 8.25 minutes of CPU time in 124 minutes of elapsed time, and our CPU runs 100% busy during month-end processing. Just in the last two weeks this job has run anywhere from 95 to 129 minutes doing the same basic work.
Elapsed time is a notoriously unstable measure of batch jobs since it depends on how busy the system is, the service class of the job, the WLM performance goal settings, I/O contention, etc, etc.
Options that may (and I emphasize, may or may not) improve elapsed time: moving datasets from tape to disk, recoding key parts of the algorithm, increasing buffers, changing service class, updating WLM. If you're serious about this, first you have to determine what's the bottleneck for your job -- is it CPU time, or is it I/O? If I/O, look at ways to improve the I/O performance and if CPU, look at ways to speed up processing within the program. And be aware that no matter what you do, if you're running during the peak processing time for your site then you almost certainly won't have much impact on elapsed time, no matter what you do.