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
If specified it must be 1-8 positions long, but if 8 a MNOTE 1 warning occurs noting that a best practice is to have the name only 1-7 positions. 1-7 positions allow the same name to be used for the MUF name optionally suffixed by a number or letter. The keyword is required when using the Simplify option (SIMPLIFY_MODE=NO not specified), and in this case the name must match the name in the CXX being used to provide security and protection of this particular environment.
This is what the installation documentation
for CA Datacom/AD says about this:
Choosing to use a full 8-byte name at this time causes the customization member AXCUSNEW to receive a condition code 1. The only way to rectify a condition code 1 is to follow the best practices by using a 1 to 7 byte name. Using the 1 to 7 byte name allows member AXCUSNEW to end with condition code zero.
The ASMSTP in this job should also have produced an MNOTE message:CXXNAME=cxxname IS OK BUT BEST PRACTICE IS 7 MAX
As a result, if there were no other errors, the configuration process can continue with the next step.