Hi Bill,
You are absolutely right. It was an old program, mission critical of course at the time, written by a good sysprog who had retired some years before. After the original author retired, changes to the program had been contracted out, but I was told that the contractor was not given the testing time he wanted. I don't know the details. It did work fine for years until we got tight on storage, but that was have been because the error routine was not being hit.. There were some tense moments spent freeing orphaned storage through Omegamon to avoid an outages. Of course, not all storage that is listed as orphaned is truly orphaned. ;-) The product was planned for replacement, so in order to mitigate the problem for the 10 months or so that we continued to run it, I minimized use of storage by some other products - moved a couple of things that were no longer heavily used from LPA to linklst, and that gave us the wiggle room we needed. It's funny though, ever notice how fast folks can get really worried when they see all of the negative testing abends? At least they notice that something is going on. Some of the products that I install are supposed to call RACF to allow/disallow access/some functions. I do thoroughly test those functions, both to make sure that they work as expected and that they don't work when they shouldn't. Sometimes it's kinda of fun to watch the violations go flying by. Linda ----- Original Message ----- From: "Bill Fairchild" <[email protected]> To: [email protected] Sent: Monday, June 6, 2011 3:56:42 PM Subject: Re: How to diagnose memory leak? Error handling routines need to be tested thoroughly and debugged as well as main routines. Bill Fairchild Rocket Software -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Linda Mooney Sent: Monday, June 06, 2011 3:21 PM To: [email protected] Subject: Re: How to diagnose memory leak? 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. Linda ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] 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 [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
