This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
MainView for DB2
BMC Performance for SQL, MainView for DB2, SQL Performance for DB2, MainView for DB2 Management, Pool Advisor for DB2, Apptune for DB2
The Data collector (DOM) fails with message BMC24384 INITIALIZATION ERROR. SERVICE:LGC-CONNECT RC: 12 and BMC24583 LGC ERROR: FUNC:LGC-CONNECT API_RC: 8 API_RSN:00000083
The BMC z/OS Configuration Component (LGC) agent queries the RTCS system registry to determine the Default DBC Group. Use the following checklist to resolve the problem:
1. Check the RTCS system registry configuration.
Enter console command RO *ALL,F RTCS,REGISTRY STATUS to determine whether the system registry VLDS is shared. The registry is shared if the OSZ0240I message displays the same dataset on each LPAR.
Verify that the RTCS members has the same SREGVLDS dataset and REGISTRY-XCF-GROUP in OSZINIxx member. Only one RTCS subsystem can dynamically allocate the system registry VLDS. When the registry is allocated and exposed, other XCF members can share the data in the system registry VLDS. If different datasets are specified in OSZINIxx and the contents of the registry are not the same, failures happen. For more information, see Controlling sharing of the RTCS system registry and Examples of configuring the RTCS system registry.
If the OSZINIxx member is updated, restart RTCS for changes to take effect.
2. Check the Default DBC group registered.
The Default DBC group is registered in the RTCS System registry and is displayed in the DBC LGCDSMPR DD sysout.
BMCLGC0000I Datastore Manager V10.1.1
Copyright (c) 2009-2012 BMC Software, Inc. as an unpublished licensed work.
BMCLGC0001I Date: Sat Dec 14, 2013
BMCLGC0080I Maint: NONE APPLIED
BMCLGC0174I RTCS Kernel Service Level is BP00254
BMCLGC0237I Default DBC Group Name: DBCRI101
If the Default DBC group is correct, go to step 3. To replace the default DBC Group, set replace="yes" in the sample provided below. See sample member LGC$REGD for the JCL. (sample uses DCPLEX as the DBC Group):
3. Check if //ZDBCssid DD statement is coded in the DBC Procedure.
Code //ZDBCssid DD statement to override the default DBC Group. For DBC JCL Procedure and LGCUTIL job, code //ZDBCssid DD DUMMY. For CLIST, code TSO ALLOC DD(ZDBCssid) DUMMY REUSE. ssid is the DBC SSID.
4. Optional. Check if RTCS private registry is registered.
The recommended approach is to use RTCS private registry for the LGC datastore. By default, the LGC datastore is stored in the RTCS system registry. See DBC LGCDSMPR DD sysout for the type of RTCS registry used for the Datastore.
BMCLGC0106I Loading Datastore from RTCS Private Registry
BMCLGC0107I RTCS Registry Information
BMCLGC0134I Backed By: LGC.DBCRI101.BMCPLEX0.LGCRGRY
To register the DBC Group's RTCS private registry for the LGC datastore, run the following sample LGCUTIL (sample member LGC$REGD). Set replace="yes" to replace the existing DBC record and <regdsn> is the dataset where the DOMPLEX optionsets will be stored. (sample uses DCPLEX as the DBC Group):
<?xml version="1.0" standalone="yes"?>
<dbc dbcgroup="DCPLEX" replace="no">