Abstract
IBM® mainframe customers span all continents, all industries, and all sizes. But one thing they all have in common is the need for the highest possible levels of availability. Achieving those levels of availability requires an infrastructure that is resilient and reliable.
In the following video, IBM Distinguished Engineer Rich Prewitt, the technical leader of IBM System z® software testing in Poughkeepsie, NY (home of the mainframe), describes the multiple phases of a piece of IBM z/OS® code from inception through general availability and beyond. Rich describes the many groups that are involved in testing z/OS code, the specific objectives of each group, and how the process moves from testing a specific function to running it in a large scale customer-like environment. Understanding the testing that IBM performs can help customers optimize the value of their own testing activities, providing more resilient systems and better value from their testing investment.
Contents
Others who read this also read
Special Notices
The material included in this document is in DRAFT form and is provided 'as is' without warranty of any kind. IBM is not responsible for the accuracy or completeness of the material, and may update the document at any time. The final, published document may not include any, or all, of the material included herein. Client assumes all risks associated with Client's use of this document.