Hi Victor,
We had a similar issue with a product that also did not handle the non-zero return code for OBTAIN properly. Each time that happened, it would orphan some storage. I used Omegamon's CSA analyzer to look at orphaned storage to identify what was going on. It did have the appearance of a memory leak, but really was not. In our case it was a problem with an error handling routine. We also use Omegamon INSPECT . Whatever you have that will look at those allocations should be helpful. We also used GFS trace after finding the Omegamon CSA entries. In our case, the product was a years old home built that had no problem previously . The problem was triggered by our increased contention for storage - an effect of adding more load to our system, so that was why it was hitting an error handler that had just not been used before. HTH, Linda ----- Original Message ----- From: "Victor Gil" <victor....@broadridge.com> To: IBM-MAIN@bama.ua.edu Sent: Monday, June 6, 2011 9:40:04 AM Subject: How to diagnose memory leak? Hi, We have an Assembler user exit invoked by a software product that runs as a long-running batch job. The exit properly OBTAINs and RELEASEs its working storage, however, as written it does not handle a non-zero return code from the STORAGE OBTAIN. This hasn't been a problem up until last week when it began to abend and the dumps indicate that there was not enough memory to allocate. Obviously, there is some sort of memory leak in the address space. Any tips on how to identify the cause are greatly appreciated. -Victor- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
