The Datacom MUF was started before Common Services completed after an IPL, causing us to get the following error message:
DB01601E CA90S MISSING OR INVALID RELEASE
I was under the impression that CAS9 was not required for the MUF startup if the module DBPCCPR could be pulled from an authorized CABDLOAD in the event it was not loaded by CAIRIM.
Release : 15.0
Release : 15.1
Component : Datacom/DB
Component : Datacom/AD
Key Common Components and Services (Common services) modules were not ready at the time the MUF needed them during startup.
Datacom needs Common Components and Services to be in place before startup. This error could be related to DBPCCPR, but there are a number of other pieces that could be involved, too.
First, as noted in the Common Components and Services Requirements of the documentation, these components are used in Datacom and more information about these can be seen in the Common Components and Services documentation:
If the CAIRIM process has not loaded DBPCCPR into memory by the time the MUF starts, the MUF will load this module into its memory. However, because it is in MUF memory and not common memory, a number of MUF functions will not work. For example, XCF processing needs DBPCCPR in common memory, and will not work if DBPCCPR was not loaded during CAS9. In addition, some security features and some DBUTLTY functions will not work.
As a result, you should ensure that Common Services processing is complete before starting your Datacom MUF (including the CAMASTER STC). There are many methods to address this, and each customer needs to determine the best approach for their business. Below are a few examples
For more information on this, please open a case for configuration information with the Common Components and Services support team.
As always, please contact Broadcom support for Datacom if you have further questions.