Skip to Content
Information
Space announcement We are no longer updating this version of the documentation for the infrastructure components (DBC, LGC, and NGL).  You can no longer leave comments on it. For the latest version of the documentation, see Common Mainframe Infrastructure 2022 release.

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

This procedure can help you determine when to assign a ZDBCssid designation for the non-default DBC group. For example, you could have your test environment use the ZDBCssid designation and your production environment registered as the defaultdbc. You must allocate ZDBCssid when invoking the product CLISTs in order to access the correct LGC product-specific registry datastore for any non-default DBC subsystem.

  1. Review the section of the installation system reference manual that describes product deployment. In this scenario, you will start by running the $300 series of jobs.Run the $$JCLCPY job to create a new JCL data set for this deployment scenario.
  2. Review product-specific configuration guides for any set up required for these products to use the DBC and its agents.
  3. 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.
  4. 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 are setting up a new LGC registry, you can customize the ALLOC step in the sample job LGC$REGD in the HLQ.LLQSAMP data set.
  5. Review Controlling-sharing-of-the-RTCS-system-registry and Determining-the-default-DBC-group.

  6. 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:

    Environment

    DBC SSID

    DBC GROUP

    defaultdbc

    XCF Group

    REGDSN

    TEST

    TST1

    TESTPLEX

    No

    TSTPLEX1

    BMCPERF.TEST.LGCRGRY

    PROD

    PRD1

    PRODPLEX

    Yes

    PRDPLEX1

    BMCPERF.PROD.LGCRGRY

  7. Consider the following details when running the $400 series of jobs, then start the DBC task as instructed in $450STRT:

    • (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 TEST, edit DBC$STC (the customized DBC started task in your JCL data set) to add the following DD statement to the PROC, wheressid is your DBC subsystem ID:

       //ZDBCssid DD DUMMY

      For example, in the TST1 installation on TEST, you would use ZDBCTST1, where TST1 is the DBC SSID. On other LPARS in this group, specify their DBC ID for ssid.

      Warning

      Note

      This step is required for any DBC group that is not registered as the default DBC.

    • For a $450STRT job, start the DBC started task.

    • If your original install specified to reuse LGC, then you will not have a $463LGCD job. You can customize the sample job LGC$REGD in the HLQ.LLQSAMP data set and run the steps that are similar to the ones from $463LGCD mentioned below.

      For PROD, run the LGCDFLT step from $463LGCD 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>

      For PROD, the LGCRGRP step from $463LGCD is shown in the following example:

         <register>                           
           <dbc dbcgroup="PRODPLEX">                                
             <rtcsreg xcfgroup="PRDPLEX1">                        
               <regdsn>BMCPERF.PROD.LGCRGRY</regdsn>  
             </rtcsreg>                                           
           </dbc>                                                 
         </register>

    • For TEST, the LGCDFLT step from $463LGCD is shown in the following example:

         <register>      
           <defaultdbc>TESTPLEX</defaultdbc>   
         </register>

      You are not required to run this step, because PROD will be registered as the default DBC. Running this step will have no effect if a defaultdbc value already exists. The value will not be replaced unless the replace='yes' attribute is in the XML.

      For TEST, the LGCRGRP step from $463LGCD is shown in the following example:

         <register>                           
           <dbc dbcgroup="TESTPLEX">                                
             <rtcsreg xcfgroup="TSTPLEX1">                        
               <regdsn>BMCPERF.TEST.LGCRGRY</regdsn>  
             </rtcsreg>                                           
           </dbc>                                                 
         </register>
  8. Run the $465INIT job.

  9. Edit the $470LGCR and $490RGIM jobs (if generated) and add the following DD statement after PGM=LGCUTIL wheressid is your DBC subsystem ID:

    //LGCUTIL EXEC PGM=LGCUTIL,REGION=0M  
    //ZDBCssid DD  DUMMY
    Warning

    Note

    (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.

  10. Continue running the $400 series jobs in sequential order.
  11. Run the $500 series jobs (if generated).
  12. Replicate the installation to other DB2 subsystems using the $700 series of jobs.See Replicating-the-installation-to-other-DB2-subsystems.
  13. Determine which method you prefer for accessing the product option sets (as explained in Working-with-option-sets):
    • (System and SQL Performance products) If you prefer to use the DOMCLIST or SPDCLIST job 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 $495SDOM started task for TEST.

      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 (or hyperlink from MainView).
      5. Navigate to Administration and then DOMPLEX Option Sets to edit and customize your DOMPLEX option set.

    • If you prefer to 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.

  14. 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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Common mainframe infrastructure 2016 release