As part of the CA Datacom/AD and CA Datacom/DB installation and configuration for each MUF, there are jobs to run to assemble the DBSYSID macro, resulting in the DBSIDPR load module (object). For CA Datacom/AD, the jobs are AXCUS01 (version 14.0), AXACTUPG and AXCUSNEW (version 15.0). For CA Datacom/DB, the jobs are BDCUSNEW and BDCUSUPG (version 14.0 and 15.0), and BDCUSNEW, BDCUSUP1, and BDCUSU15 (version 15.1).
After running my customization job, the assembly of the DBSYSID macro produced a CC 1 in ASMSTP, and the LNKSTP completed with a CC 0. Is there a problem with the assembly?
There is no problem here. The CC 1 is the result of using an 8-character MUF/CXX name.
In the CA Datacom/DB administration documentation, the section Modifying DBSIDPR Parameters entry for CXXNAME says:
As always, please contact CA Technologies support for CA Datacom if you have further questions.