Why does CA Datacom/AD have a different EOS (End of Support) date than CA Datacom/DB?

Document ID : KB000011719
Last Modified Date : 14/02/2018
Show Technical Document Details

Why does CA Datacom/AD have a different EOS (End of Support) date than CA Datacom/DB?


The CA Datacom/AD product, designed to support CA Technologies products, is built upon the same code base as CA Datacom/DB. However, while the DB product components and configuration are dynamic and subject to frequent changes (due to tuning, enabling new features, etc.), the AD product components are quite fixed, and are changed typically only with base product upgrades or changes. In general, there are very few fixes created for AD alone; the greatest majority of the fixes are for the various DB product components.

For any particular release level, the GA release of AD usually follows DB by several months, allowing the DB product to “settle down” and burn in at a number of clients. We then perform rigorous testing internally and through client Beta tests on the “proposed” GA version of AD. The intent here is to offer an AD product level that requires a minimum amount of maintenance effort during its usage (although a number of clients will still keep their version at current maintenance levels).

Finally, since most of the fixes for a release level will be for the DB product components, there is no real need to end support (EOS) the AD product at the same time as the DB product. We expect that supporting AD even after DB has reached EOS will not be a problem, and don’t expect new problems to arise in the base DB code as used by the AD customers. By setting the product EOS status, we can reallocate our R&D resources to the new releases, making an even better product! The end result is that the AD customers will have several more months of support on their version, and can better plan their upgrade path.

Additional Information:

As always, please contact CA Technologies support for CA Datacom if you have further questions.