Replicating the installation to another sysplex on non-shared DASD

For example, in Product deployment scenarios involving infrastructure, the DBCs for SYSPLEX X1 are already operational and you want to replicate it to SYSPLEX X3.

1. Review the section of the Installation System Reference Manual that describes product deployment. In this scenario, you are deploying at the SYSPLEX level. so you will start with running the $300 series of jobs.
2. Run the $$JCLCPY job to create a new JCL data set for this deployment scenario.
3. If necessary, use your own process to transport the runtime data sets to the other environment.
4. Modify the infrastructure symbolic variables as follows:
   1. In Symbolic variables contained in $$INCINF member, locate the rows that contain the entry 'Different DBC started task,' 'Different DBC Group,' or 'Different DOMPLEX NAME' in the fourth column.
   2. Use the symbolic variables in the second table column of those rows.
5. Begin running the installation jobs with the $300 series of jobs, as follows:

   • (For System and SQL Performance) Review the $310VDOM job. If your original install specified to reuse the DOM VSAM data sets, but you need to create new ones, then contact BMC Customer Support for a sample job.

   • (For LGC) If your original install specified to reuse LGC, then you will not have a $310VLGC job. If you need to create a new LGC registry for this environment, you can customize the ALLOC step in the sample job LGC$REGD in the HLQ.LLQSAMP data set.

6. Run the $400 series of jobs and consider the following:

   • (For NGL) If your original install specified to reuse NGL, then you will not have a $410VNGL job. If you do not have a $410VNGL job and you need to create a new one for this environment, contact BMC Customer Support for a sample.

   • (For LGC) If your RTCS system registry is not shared with the original LPAR, run the $463LGCD job. If your original install specified to reuse LGC, then you will not have the $463LGCD job. If you are setting up a new LGC registry, you can customize the sample job LGC$REGD in the HLQ.LLQSAMP data set.

   • (Before running the $490RGIM job (if generated)) If your original install specified to migrate LGC option sets for your products, the job will copy the option sets from the previous version to the new version and then update certain values for new data set names, plan names, and so on. If your new environment does not have any option sets to migrate, contact BMC Customer Support to get a sample job that will create a new option set.

7. Run the $500 series of jobs (if generated).
8. Replicate the installation to other DB2 subsystems using the $700 series of jobs.

   See Replicating the installation to other DB2 subsystems.

9. Verify that the products are working correctly:

   • Check the DBC log and DBCPRINT for messages to ensure that the product agents are running successfully.

   • Invoke the product CLIST (if applicable) or run a batch job to verify that the products are working correctly.