If a job executes in parallel threads on multiple CPUs, the CPU time could be more than the elapsed time.
A massive number cruncher could run for an hour and consume 59 minutes of CPU. An interactive application that waits on a user could run for an hour and consume only seconds of CPU. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lindy Mayfield > Sent: Sunday, April 09, 2017 9:42 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: CPU Timerons/Seconds vs Wall-clock Time > > I only have CPU time from SMF 30 but I don't have elapsed time which is very important. > I'd like to somewhat infer that a high CPU time means the job ran a long time. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
