> if the requested storage that caused the heap to expand gets returned with a > free() or delete I do not believe the C runtime issues a STORAGE > RELEASE for the additional increment of heap: it keeps it around in > anticipation of future malloc() or new requests. It does not RELEASE the > heap storage until the enclave ends.
You can control that with the FREE option on the HEAP LE runtime option. See z/OS 2.2.0>z/OS Language Environment>z/OS Language Environment Programming Reference>Language Environment runtime options>Using the Language Environment runtime options>HEAP. http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ceea300/clheap.htm?lang=en-us "KEEP Specifies that an increment to user heap storage is not released when the last of the storage within that increment is freed. FREE Specifies that an increment to user heap storage is released when the last of the storage within that increment is freed." KEEP is the default. -Carl ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
