ECC overview
All components of ECC are installed together using the single install image. ECC consists of a single FMID (MLCXnnn) for all components, operating from one authorized load library (SLCXAUTH) and one non-authorized load library (SLCXLOAD). CMSC, LMS, HCI, CSS, and BMC AMI Base Services are all on the same release level.
We recommend that you activate and configure all the ECC components at the same time to avoid compatibility issues between different release levels. Which components of ECC you need to activate and configure depends on which BMC AMI products are licensed by your organization.
ECC is installed using SMP/E, facilitated by the BMC AMI Installer. Each ECC component can be configured individually, depending on your site’s requirements.
The following are the components that ECC is connected to:
- BMC AMI Common Mainframe Services Controller (CMSC) is required for any BMC AMI mainframe product, version 17.02 or higher, as those products use PARMLIB and also if you are using zAdviser.
- BMC AMI License Management System (LMS) is required for any BMC AMI mainframe product, in order to verify that the corresponding License Certificate exists, enabling use of the product.
- BMC AMI Host Communications Interface (HCI) is required to facilitate communications between a distributed BMC AMI product (for example, BMC AMI DevX Workbench for Eclipse) and mainframe BMC AMI products.
- BMC AMI Common Shared Services (CSS) is required for sharing compiled program information for BMC AMI products (for example, Code Debug).
- BMC AMI Base Services is required to support CMSC and BMC AMI DevX Abend-AID.
This section provides information about the following topics: