Determining the default DBC group for LGC

You can have only one default DBC group per RTCS system registry. After the default DBC group is established, changing it can have unexpected results.

Establishing a default DBC Group in the RTCS system registry allows products to obtain their option sets from LGC without having to specify a DBC to connect to. The product will always connect to the default DBC unless a DBC SSID parameter is used.

If you have more than one DBC started task on an LPAR, or have multiple DBCs in the same sysplex using different DBC groups and the RTCS system registry is shared, only one DBC can be registered as the default DBC. If the LGC option sets for any LGC clients are in a different LGC registry from the default DBC, then those DBCs will need to use a special ZDBCssid designation. For more information, see Replicating-the-DBC-by-using-a-different-DBC-group.

If you are not certain which DBC group is the default, use the following procedure to find the default.

Related topic

Modifying-infrastructure-components

To find the default DBC group

  1. Edit the LGC$LIST member from the SAMP data set to contain the following input:

    <lgcutil>
    <list><dbc /></list>
    </lgcutil>

  2. Run the job and then examine the LGCUTLPR output.
    The name of the default DBC group (DCPLEX in the following example) is marked with an asterisk.

    BMCLGC0178I DBC GROUP & SSID  DATASTORE (private registry or z/FS path)     XCF GROUP
    BMCLGC0179I ----------------  --------------------------------------------  ---------  
    BMCLGC0180I DCPLEX*           LGC.DEV1011.RTCS.REGISTRY                     LGCGRP1
    BMCLGC0180I DMRQAGRP          DMRQA.DB2A.PLEX1.REGISTRY                     DMRQ@GRP
    BMCLGC0180I UBF1PLEX          DIS.IVP101.DEBF1.LGCRGRY                      BF01@
    BMCLGC0182I 3 DBC system(s) matched the search criteria   
    BMCLGC0183I * Default DBC group name


 

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