Overview of DB2 Product Configuration (LGC)

Through its online interface, LGC simplifies configuration. You can accept the default option values or make changes to them, if needed.

LGC panels simplify navigation by allowing you to expand or contract sections as needed. You can link to LGC from within your product or solution to maintain a consistent look and feel, and to retain your changes from version to version.

LGC operates as an agent within the DBC subsystem. The LGC agent uses the Registry Component of the Runtime Component System (RTCS) to access the RTCS Subsystem system registry or, optionally, a private RTCS-managed registry. LGC stores the option sets for many BMC products in a datastore (a collection of XML documents), which is stored in one of the RTCS-managed registry instances.

LGC can use a private, shared RTCS-managed registry, which uses the MVS cross-system coupling facility (XCF) to communicate with other LGC agents in the sysplex defined to the same DBC group. A private registry instance in one and only one LGC agent at a time owns (dynamically allocates and performs all I/O) the backing VLDS for the RTCS-managed registry which contains the LGC datastore. If the owning agent is stopped, an RTCS registry instance in another LGC agent in the same DBC group assumes ownership of the registry after first dynamically allocating its backing VLDS. If LGC is using the RTCS Subsystem system registry for the LGC datastore, the RTCS Subsystem address spaces manage their common registry instances and the single sysplex-shared backing VLDS.

The FMID that corresponds to the LGC technology is ZLGCxxx, where xxx represents release number information.