Typically, when a program is tested, program load modules are promoted through different stages before reaching production. For example, when a new program is compiled for the first time, it might be placed into a test load library. After unit testing is completed, perhaps the compiled program is promoted to a quality assurance environment. And eventually, it is promoted into production. On your system, you might know these stages by different names, such as:
Consider whether you want the ability to use Debug Tool for z/OS, Fault Analyzer for z/OS and Application Performance Analyzer for z/OS throughout your programs' life cycle. Even if you do not plan to use Debug Tool for z/OS with production programs, Fault Analyzer for z/OS and Application Performance Analyzer for z/OS are very useful in those stages. To enable the IBM Problem Determination Tools products at each stage, update your promotion processes to retain the source information files. Promotions can be accomplished by performing a recompile, a copy, or a move. Perform the same steps with your source information files that you perform with your load modules or object modules. For each load library or object library, you should have a corresponding set of source information libraries. Whenever you promote a load module or object module, you should promote the source information file as well. This ensures that the source information file is available for Fault Analyzer and Application Performance Analyzer, and you can continue to take advantage of the IBM Problem Determination Tools products at all stages of your program's life cycle.
[ Top of Page | Previous Page | Next Page | Contents | Index ]