I have seen that happening with JVMs in regions, e.g. comparing 384M and 512M and 0M. So if you don't find any logic in the COBOL source that does its own allocation, its very likely the runtime. dg. -----Original Message----- From: Tom Marchant <0000000a2a8c2020-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU> Sent: Tue, Jul 25, 2017 3:40 pm Subject: Re: REGION=0M leads to CPU through the roof
On Mon, 24 Jul 2017 15:33:55 -0700, Gerhard Adam wrote: >Since the amount of storage was nearly 50 times greater than the original, it >seems that the program is clearly managing [or searching] are large amount of >storage that it doesn't need. It seems that that might account for the CPU >time increase. > >I see no reason why a program that successfully ran using the default region, >should suddenly allocate all the available memory just because 0M was coded. > >Even though you said the increase in storage was not surprising, it actually >is. I agree. Increasing the region doesn't ordinarily increase the storage utilization. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
