The assembly of the DBSYSID macro , to generate load module DBSIDPR, produces a CC 1 in ASMSTP, and the LNKSTP completes with a CC 0.
Is there a problem with the assembly?
z/OS
Using an 8-character CXX name and MUF name.
There is no problem here. The CC 1 is the result of using an 8-character MUF/CXX name.
The ASMSTP in this job produces an MNOTE message:
CXXNAME=cxxname8 IS OK BUT BEST PRACTICE IS 7 MAX
For documentation , see Modifying DBSIDPR Parameters.
In the Datacom/AD documentation, Prepare Product Custom Assemblies, there is this note:
The only reason known to cause the Condition Code (CC) 0001 is when the CXX name is 8 bytes in length. The CXX name and the MUF name are used for this process by the same 9CXX_NAME symbolic name. The second to last step in this JOB is the step that generates a CC 1 because the name is 8 bytes in length. If CC 0000 is desired from this process, follow best practices for the CXX name.