You might need to execute some of the remaining tasks. For instance, if you maintain a second-level z/VM system with its own z/VM software and server for testing the latest CA product maintenance (or an individual APAR) this system should be generated by generating the Test System. After verifying the effect and reliability of the maintenance, you would migrate the Test System software to your Production System and regenerate your first-level system using selected tasks from the Production Task Selection Menu.
You might also have several different production z/VM systems, each with a different hardware or software configuration. In this case, you would execute one or more installation tasks to define a target production system, generate that system (or a portion of it) then repeat this sequence for another target system.
In this case, you should be sure to test the new software with all required configurations before copying to the Production minidisk.
It is possible that your production environment is used, off-hours, for testing new levels of the Test System software. After testing, these generated systems might be moved directly to production use. This is permissible provided that you maintain sufficient controls and testing procedures.
|
Copyright © 2013 CA.
All rights reserved.
|
|