I am not sure that looking at one SMF record can tell the story. If the job ran long, was it due to
I/O Looping Code Larger than normal Data Load And so on. Maybe other can provide better insight. Lizette > -----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. > > /Lindy > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: sunnuntai 9. huhtikuuta 2017 18.55 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: CPU Timerons/Seconds vs Wall-clock Time > > What are you trying to solve? > > Jobs get swapped in and out depending on what work they are doing. > > > Are you trying to relate wall clock to cpu time? I have seen jobs run 2 hours > wall clock time and only take 10 mins of CPU time. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Lindy Mayfield > > Sent: Sunday, April 09, 2017 8:48 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: CPU Timerons/Seconds vs Wall-clock Time > > > > This may or may not be the dumbest question I've asked this week, but > > I've been working with Linux a lot lately so that's my excuse. > > > > For example, if an MVS job ran and consumed 10 CPU seconds (SMF 30 I > > think), can I assume that it at least took 10 seconds of elapsed time to > run? > > > > Regards, > > Lindy ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
