What's strange to me, is that the program used up all the available storage indicated by coding REGION=0M. This clearly means that the program is dynamically adjusting the amount of storage that it needs based on the available region. After all, if it were of fixed size, then coding 0M wouldn't have any effect on what was going used.
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. Adam -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Allan Kielstra Sent: Monday, July 24, 2017 3:28 PM To: [email protected] Subject: Re: REGION=0M leads to CPU through the roof Do you have access to Application Performance Analyzer (APA) or Strobe (or FreezeFrame)? If not, can you cut the program down to some kernel that exhibits the same characteristic? Also, do you happen to have COBOL V5 or V6 (maybe the trial version)? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
