Not playing word games with you but if reading the JES log is your measurement process, then you have a measurement process and that is it.
Not trying to insult you here but I have managed to shoot myself in the foot from time to time on trivial things: ran the wrong job, looked at the wrong job output, etc. If it were me and I was confident of my "measurement" (however you want to define that) then I would PMR it. Do you have the source for the program? Is there "modern" COBOL cleverness in there? Dynamic tables, that sort of thing? Here's a scenario: clever COBOL program determines region size and allocates a table that just fits. Due to a bug or bad design, it is searching or clearing the entire table repeatedly. The bigger the region the greater the time. Is the problem specific to REGION=0M or does simply increasing the region size somewhat make the CPU time go up a little? Yes would point to a scenario such as my previous paragraph. No would point to some bug specific to REGION=0M. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Way, Richard Sent: Monday, July 24, 2017 3:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: REGION=0M leads to CPU through the roof There's no "measurement process" per se - I'm reporting the data as indicated directly from the job log. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
