Ed Gould wrote: >Seriously the issue is absence of debugging tools to find the leak >seems like it would be simpler to have them.
Who said they didn't? They had quite excellent problem determination tools (plural). Keep in mind the mission-critical application was in production. Neither planned nor unplanned downtime was/is tolerable. They had to keep the business service available while troubleshooting and then fixing the problem. They did, and the platform made possible their Apollo 13-like triumph. Failure would have been quite expensive. Clark Morris wrote: >The joy can be understanding why the bug, fixing it so that you don't >cause the application equivalent of the PE chain, running all the >tests and then going through change management. Setting up the >appropriate tests alone can be time consuming. Quite correct, I agree. Radoslaw Skorupka wrote: >Price is also a problem.... Yes, I suppose the price of the levee that would have saved New Orleans was "a problem." The price of Hurricane Katrina was much higher. Even so, I assume you'll be pleased IBM has majorly reduced the price of memory, even while it's the only memory in the industry with RAIM protections, to pick one among several unique characteristics. Enjoy. It's *always* about value for money, whether mainframes or moon rockets. This isn't a complicated concept. Now raise your hand if you want the lowest priced heart surgeon, operating room, and artificial valve. :-) -------------------------------------------------------------------------------------------------------- Timothy Sipples IT Architect Executive, Industry Solutions, IBM z Systems, AP/GCG/MEA E-Mail: sipp...@sg.ibm.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
