Replicating the DBC (for a different DBC group) by using a ZDBCssid designation

Assume that you have the following environment, and that you want to set up TEST to specify ZDBCssid and let PROD use the default DBC group:

1. (Optional) Run the $200ALOC-series of jobs.
   
   Run these jobs if you changed the runtime HLQ and you plan to create new runtime data sets populated from the original SMP/E target libraries.Otherwise, copy the current runtime libraries to the runtime libraries for the new environment. A new set of runtime libraries allows you to deploy maintenance in a controlled manner from one environment to another at separate times. Use your own process to transport the runtime data sets to the other environment if necessary.
   
   
2. (Optional) Run the $300SPLX-series of jobs.
   
   Run these jobs if you are deploying to a new SYSPLEX environment.For System and SQL Performance products that use the DBC, the $310VDOM job should be run if you are deploying to a different DBC Group that would have its own runtime data sets.
   
   
3. Run the $420INF job.
   
   The $420INF job creates the DBCENV data set referenced on the DBC$STC procedure and copies the customized pppvvrm members (where ppp is the 3-character product code and vvrm is the version, release, and maintenance level of the product being installed) to it for the infrastructure products. It will also copy customized procedures and CLISTs from the JCL data set to user library data sets.By default, the Installation System allocates the DBCENV data set containing the &SYSCLONE symbolic variable, so it is important to run this job on the target LPAR. Using SYSCLONE allows maintenance to be deployed by LPAR. 
   
   
4. Review the comments in the $450STRT job to determine if the DBC needs to be restarted.
   
   The $450STRT job contains instructions for starting the DBC. Comments explain different upgrade scenarios. For example, the DBC does not need to be restarted if it already references the DBCENV data set and none of the products being installed require updated infrastructure maintenance (DBC, LGC, or NGL).
   
   
5. After the DBC is started and LGC is active in the DBC, perform the following steps:
   
   
   1. Customize the sample job LGC$REGD in the HLQ.LLQSAMP data set by using the following input.
      
      

   2. For PROD, run this register step first to establish it as the defaultdbc.

      <register>      
         <defaultdbc>PRODPLEX</defaultdbc>   
      </register>

      If a default DBC has already been registered, an error message will notify you. To replace the existing defaultdbc value with a new one, add the replace attribute to the XML:

      <register replace="yes">     
        <defaultdbc>PRODPLEX</defaultdbc>  
      </register>
6. Run the $490TRIG job when you are ready for the DBC and its agents to be upgraded.
   
   Everything prior to this job can be staged. This job will update the DBCPRODS member in the DBCENV data set which tells the DBC which product versions to define. Once this job is run, the DBC will begin defining or redefining the products that have been installed new or upgraded and stop and start the agents.
   
   
7. Run the $500 series 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. Determine which method you prefer for accessing the product option sets (as explained in Working-with-option-sets):
   
   
   1. (System and SQL Performance products) If you prefer to use the DOMCLIST or SPDCLIST in the UBMCCLIB data set, complete these steps:

      1. Edit the DOMCLIST or SPDCLIST to change the top of the PROC statement to automatically connect to your DBC subsystem.

         Having separate CLISTs for the test and production environments forces TEST to connect with TEST and PROD to connect with PROD. Use the following statement, where domplex is your DOMPLEX option set name:

         PROC 0 P('PRD=,DP=domplex') SSID()

         For example, you could use the following statement for TEST:

         PROC 0 P('PRD=,DP=TESTOPT') SSID().

         Warning

         Note

         The DOMPLEX name should match the DOMPLEX keyword value in the DOMOPTS member located in the DBCENV dataset used by the TEST DBC started task.

      2. (Required for any DBC group that was not registered as the default DBC) Add the following allocation to your product CLISTs (DOMCLIST, SPDCLIST, or DOMC) to connect to your LGC component:

         ALLOC F(ZDBCssid) DUMMY REUSE

         Also, add a FREE statement at the bottom, where ssid is your DBC SSID:

         FREE F(ZDBCssid)

         For example, TEST would use the following statements:

         ALLOC F(ZDBCTST1) DUMMY REUSE
         FREE F(ZDBCTST1)

      3. If you want to use the same CLIST for multiple LPARS, add code similar to the following example, and then use similar IF statements at the end of the CLIST to free the allocation:

         IF &SYSNAME=DB2A THEN +
            DO
              ALLOC F(ZDBCTSTA)DUMMY REU
            END
         IF &SYSNAME=DB2B THEN +
            DO
              ALLOC F(ZDBCTSTB)DUMMY REU
            END

         In this example, TSTA is the DBC ssid on LPAR DB2A and TSTB is the DBCssid on LPAR DB2B.
         
         

      4. Execute the DOMCLIST or SPDCLIST.
         
         
      5. Navigate to Administration and then DOMPLEX Option Sets to edit and customize your DOMPLEX option set as desired.
         
         In the dialog task bar, if you click Help and choose About, it will display the DBC that is being accessed. Verify that the correct DBC is listed.
         
         

   2. If you use the LGCISPF CLIST in the product UBMCCLIB or UBMCSAMP data set, specify the DBC ssid to use, as shown in the following example:

      EX 'BMC.BMCCLIB(LGCISPF)' 'DBC(ssid)'

      In this example,ssid is the DBC subsystem identifier. The DBC that you specify must be active in the LPAR.
      
      

10. After completing all the jobs to deploy the products, verify that the products are working correctly:
    1. Check the DBC log and DBCPRINT for messages to ensure that the product agents are running successfully.
    2. Invoke the product CLIST (if applicable) or run a batch job to verify that the products are working correctly.