> Elapsed time will ALWAYS be longer than CPU time.


This is only true if there is no multitasking / multithreading in the job. 
Lindy asked quite generally if a job's elapsed time would always be longer than 
the cpu time it used. And the general answer would be no.


My DB2 colleagues run DB2 reorgs as batch jobs. Just lately, I saw one of these 
job using 670% (yes, that is six-seven-zero) of cpu over a really long time 
(can't check the exact number right now). If that job would be given the 
access, the cpu usage in say 30 minutes of elapsed would be some 200 minutes.



An extreme example, I admit.


--
Peter Hunkeler




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to