IMS Version to Version Migrations and Installations
There are many sound reasons why a customer will move from the old version of a software product to the next version or the current version of the product. Enhancements and new functions get added to the new version or the old versions support gets dropped. GSC will plan the migration phases with the customer, the new product will be migrated or installed into a test environment, and all of the current maintenance will be installed on that test system. All of the jobs will be created automatically and some manually through an installation program. These jobs will be customized accordingly to the customer’s specifications, to reflect the library names and dataset names that the customer would like to use. The output from that execution will be input to stage2 system definition, this step will create a lot of your libraries and link-edits the load modules and control block modules. Your system is built at this point. Customization of your startup JCL, and identifying what applications will be tested will now start. Once the testing phase has been completed to the customer’s satisfaction, the current production system will be moved onto the newly installed test system, this will now become the production system.