Updating your promotion process

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 QA environment. Finally, it is promoted into production. On your system, you might know these stages by different names, such as Unit test, System test, and Model office.

Consider whether you want the ability to use z/OS® Debugger, Fault Analyzer, and Application Performance Analyzer for z/OS® throughout your program's lifecycle. Even if you do not plan to use z/OS® Debugger with production programs, Fault Analyzer and APA are useful in those stages. To enable the ADFz 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, have a corresponding set of source information libraries. Whenever you promote a load module or object module, promote the source information file as well. This ensures that the source information file is available for Fault Analyzer and APA, and you can continue to take advantage of the ADFz products at all stages of your program's lifecycle.