Here's the link I failed to include, the suggested reading: http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ceeam00/clsthp.htm
An overview, but, for the willing reader, follow the references and go as deep as you want. LE can report on storage used, and storage (like heap) definitions can be tuned from the reports. You don't (you can, occasionally, but probably mostly not at all) run in Production with the reporting on, due to overheads. It is an LE run-time option, so no recompiles or anything needed. You can use the report to make the initial heap allocation sufficient for the enclave. Then you only get one OS request to get the storage, and LE managing the storage thus acquired. When servicing more complex memory requirements (non-batch, large amounts of memory, need for release) the definitions can be more complex. If you have some heap which gets corrupted, you can get LE to check everything as it goes along, and tell you as soon as something goes awry. Effective way of finding out around about where it gets tangled. You do this only when you know you already have a problem. It heavily impacts performance of heap usage, checking each reference made to heap storage to confirm all is still consistent for LE. Again LE run-time option. Don't use all this type of stuff regularly, just because you can. These things are not proactive monitoring tools, but analysis (storage report) and determination (heap busted) tools. Know what is available, so you know what to use when/if needed. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
