BMC24384 INITIALIZATION ERROR.  SERVICE:LGC-GETOPTION

Version 1
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    SQL Performance for DB2


    APPLIES TO:

    SQL Performance for DB2, System Performance for DB2, MainView for DB2, BMC Performance for SQL, MainView for DB2 Management, Apptune for DB2 (all supported versions)



    PROBLEM:

     

    DOM (Data Collector) fails to initialize when the DOMPLEX optionset is not found in the LGC datastore.

    DOM product agent issues:
    BMC24384 INITIALIZATION ERROR.  SERVICE:LGC-GETOPTION   RC: 8 or 12

    LGC product agent issues:
    BMCLGC0027E Option set "DCPLEX" for "DOM 1120" not found

     


    SOLUTION:

     

    DBC started task LGCDSMPR sysout, the SYSPRINT for the LGC data store manager displays the LGC messages. For e.g:

      
    BMCLGC0174I RTCS Kernel Service Level is BP00246
    BMCLGC0237I Default DBC Group Name: DCPLEX 
    BMCLGC0106I Loading Datastore from RTCS System Registry             
    BMCLGC0107I RTCS Registry Information
    BMCLGC0134I Backed By: SYS3.MAINVIEW.RTCSRGRY
    BMCLGC0135I XCF Group: OSZRTCSR, Connection Member: RTCS004ES10F, Owning Member: RTCS004FS50M
    BMCLGC0136I Status   : REMOTE, SHARED, NOT EXPOSED
    BMCLGC0174I RTCS Kernel Service Level is BP00246
    BMCLGC0137I Datastore successfully loaded
    BMCLGC0019I The following products and option sets are installed 
    BMCLGC0039I Starting OptionSet Manager
    BMCLGC0038I OptionSet Manager is now active
    BMCLGC0038I Datastore Manager is now active
    BMCLGC0027E Option set "DCPLEX" for "DOM 1120" not found 
      

    Check the following:

      

    (A) RTCS System Registry     

      
       
    1. Issue console command RO *ALL,F RTCS,REGISTRY STATUS to determine if the registry is shared. The registry is shared if the OSZ0240I messages show the same dataset on each LPAR.
    2.  
    3. The RTCS members that share a registry must have the same SREGVLDS dataset and the same REGISTRY-XCF-GROUP in OSZINIxx member.
    4.  
    5. Ensure that the same physical dataset is shared by all the members. In a nonshared-DASD environment, it is possible to have the same dataset names but different physical datasets. Refer to Controlling sharing of the RTCS system registry and Examples of configuring the RTCS system registry.
    6.  
    7. Restart RTCS for changes to take effect.
      

    (B) RTCS private registry (LGC) 

      
       
    1. Verify Default DBC Group 
      
      The LGC product will always connect to the default DBC Group and use the LGC registry dataset registered for the datastore. Each Sysplex can have more than one DBC Group. BMCLGC0237I shows the default DBC Group. If there is only one DBC Group and the default DBC is registered, skip to step 2. Otherwise follow these steps: 
      
       
    1. Run sample member LGC$REGD to register or replace the default DBC Group. 
    2.  
    3. The DBC procedure and LGCUTIL jobs need the //ZDBCssid DD DUMMY to direct LGC to the correct datastore. Refer to Overview of using ZDBCssid to designate non-default DBC groups. E.g PRDPLX and TSTPLX DBC subsystems use separate runtime datasets, option sets and LGC registry. PRDPLX is the default DBC Group. Therefore the TSTPLX DBC subsystems require the ZDBCssid statement.
    4.  
    5. Refer to Replicating the DBC using ZDBCssid designation Step 13 for specific instructions to customize the CLISTs.
      
       
    1. Verify LGC private registry and its XCF group
      
      BMCLGC0106I shows the type of RTCS registry: RTCS private registry or RTCS system registry.  
    BMCLGC0134I shows the RTCS registry dataset name.  
    BMCLGC0135I shows the XCF group and the XCF members.  
    BMCLGC0136I shows the RTCS registry as SHARED or UNSHARED.  
    The RTCS Private registry is recommended for the LGC datastore. If there are no changes to be done, skip this step.  
      
       
    1. Run sample member LGC$REGD  to allocate a private registry and register or change the DBC Group entry. Ensure the same physical dataset is shared by the XCF members. 
    2.  
    3. Run sample member LGC$BKUP to backup the LGC datastore. 
    4.  
    5. Recycle the LGC agent using console command dcssid LGCREFRESH. 
    6.  
    7. Run sample member LGC$IMPT to import data into the new LGC datastore. 
      

    Once steps (A) and (B) are complete and the DOMPLEX optionset is still missing, follow these steps:
    BMCLGC0019I to BMCLGC0021I lists the products and option sets stored in the LGC datastore. 

      
       
    1.  Run install job $490RGIM to register DB2 products and create/migrate the optionset depending on the install customization.  
    2.  
    3.  If there is no optionset to migrate, sample member LGC$IMPT contains JCL to create a sample option set. Edit the job to point XMLIN to hlq.BMCXML(DOMSAMP). Then modify the sample optionset using DOMCLIST or LGCISPF clist. Refer to Working with LGC - accessing online interface and Working with DOMPLEX option sets Task Summary
    4.  
    5. Restart the DOM agent using console command dcssid DOMREFRESH for changes to take effect.

     


    Article Number:

    000093157


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles