Thanks to everybody for your support. As usual I learnt a lot. The problem was (as usual business) between my seat and my keyboard. The PLI FREE statement was not consistent with ALLOCATE. The size of the area to be free was not correct. I thought it was not so important and I was wrong. The manual states it counts.
Anyway my program suffers of HEAP fragmentation because of a mix of (lot) small areas that I often need to allocate and free and (few) big areas that I need to free and allocate rarely (root cause of the problem). To trigger the issue I ran the program with a small region size, hopefully with a bigger region I'll run ok. It seems there's no way to ask PLI/LE for heap defrag. Best regards. Max. Il giorno dom 5 mar 2023 alle ore 22:07 Seymour J Metz <[email protected]> ha scritto: > VSMLIST is certainly the best way to test what z/OS has allocated in large > blocks, but I believe that the OP would be better served by using PL/I > facilities to allocate and report the storage. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Discussion List [[email protected]] on behalf > of Peter Relson [[email protected]] > Sent: Saturday, March 4, 2023 9:13 AM > To: [email protected] > Subject: Re: Virtual Storage Manager - LDA. > > Updates to the LDA are done synchronously with respect to the request. > Fields such as LDALOAL, LDAHIAL, LDAELOAL, LDAEHIAL might be of interest > depending on what you're doing (subpool and whether the virtual is above or > below 16M, in particular). I don't recall, but those might reflect > allocation of anything within a given page rather than indicating the exact > number of bytes allocated. > > If you want details from a program, use VSMLIST. Or take a dump and look > at one of the IPCS VSMDATA reports. > And GTF tracing of getmain/freemain/storage requests is available to you. > > Peter Relson > z/OS Core Technology Design > > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
