Migrating to production
This topic discusses some considerations that you should review before you migrate an APPLICATION RESTART CONTROL (AR/CTL) product from a test environment to a production environment. It also discusses the tasks involved in the migration process.
Migration considerations
Before you migrate an AR/CTL product to a production environment (or a product-acceptance testing environment), BMC recommends that you check the product components listed in the following table to ensure that the product functions correctly in the new environment.
Product component verification
Step | Component | Task |
|---|---|---|
1 | Product data set names | Ensure that all references to product data sets indicate the names of the new data sets in the production environment where the product modules reside. This task includes changing data set names in environment registration records if you copy records from a test REGISET to a production REGISET. |
2 | CPU authorization | Ensure that the products being migrated are authorized for use on the CPU where the production system resides. For questions about CPU authorization, contact your BMC sales representative. For more information about the authorization process, see the Installation System documentation. |
3 | Dynamic allocation skeletons | Ensure that the dynamic allocation skeletons are appropriate for a production environment. For more information about setting up dynamic allocation skeletons, see the following sections: |
4 | Global processing option values | Ensure that the processing option values specified in the global processing options record for each product are appropriate for a production environment. For more information about setting option values, see the following sections: |
5 | LIBDEF table | Ensure that all references to product data sets in the LIBDEF table indicate the names of the new data sets in the production environment where the product modules reside. |
6 | Enhanced processing | To use enhanced processing with AR/CTL products, ensure that enhanced processing has been installed on the CPU where the production system resides. If you plan to use enhanced processing, ensure that enhanced processing is reactivated each time an IPL is performed. |
7 | Product security | To use the security facility provided with the AR/CTL products, determine whether you want to use the internal security component or the external security component. If you plan to use the external security component, ensure that the security settings are consistent with the RACF settings on the production system. For more information on product security, see Administering. |
8 | Remote VSAM access implementation | Ensure that remote VSAM access implementation is performed in the production CICS regions as described in Implementing remote VSAM access. |
Migration of an AR/CTL product to production
Migrating an AR/CTL product from a test environment to a production environment usually consists of the following tasks:
Comments
Log in or register to comment.