CA Datacom needs CA Common Services components to be in place before it will completely start. 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 Prepare for Installation section
of the documentation, these components are used in CA Datacom:CA Health Checker
This component provides checks and advice for best performance of the product. CAMASTER is part of this component.CAICCI
This component allows your CA products to work together across platforms, making your software more powerful.CAIENF
, CA LMP
, and CAIRIM
These components assist you in getting your CA products running and keeping them running. CAIRIM is required for CA LMP support. Mainframe products require CA LMP.CAISSF
This component enables your CA products to offer standardized security interfaces.
Then, your comment about the loading of DBPCCPR is correct, but the statement is incomplete. 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 CA Datacom MUF (including the CAMASTER STC). If you are using an automated operations tool, you should be able to set this parent/child relationship to prevent the MUF from starting too soon. Another option if you will always start your MUF when CAS9 runs is to have the CAS9 job start the MUF once it is initialized. For more information on this, please open case for configuration information with the CA Common Services support team.