In running a maintenance job against my MUF, I received an error
DB10092E - CXX NAME MISMATCH, SID=ADMUF1J CXX=CA11MUF
My MUF is running fine, so how do I correct this?
Component : CA Datacom/AD
Component : CA Datacom/DB
This error is caused by using a DBSIDPR module that was assembled with a CXXNAME value different from the CXXName stored in the control block of the CXX file.
There are different ways that this error could appear. The first set of possibilities is the result of using the wrong files, so verify these first:
If all of these are correct, then you can look at the CXX file itself to see what its name is. For SIMPLIFY_MODE=YES, get the value of DSN_XXX from the MUF log, in this message:
DB00254I - SIMPLIFY . . . DSN_XXX=DCMLV1.JOHDO10.BD1510.DJMU1DF.???
Replace "???" with "CXX" and this will be the DSN for the DD1 statement below. If not using Simplify mode, get the DSN for the CXX from the MUF JCL and enter it here.
//DBUTLTY EXEC PGM=DBUTLTY,REGION=0M
//STEPLIB DD DISP=SHR,DSN=<your MUF STEPLIB CUSLIB...
// DD DISP=SHR,DSN=<your MUF STEPLIB CAxxLOAD...
//DD1 DD DISP=SHR,DSN=xxxxxxxxxxxxxxxxx.CXX <<---Change as indicated above
//SYSIN DD *
REPORT TYPE=U,DDNAME=DD1
/*
After running this program, you will get output that indicates the CXX internal name at the top of the report, on the right side:
DEVICE INIT DATE TIME CXX NAME
3390 20130623 054626 CA11MUF
As a verification, you should see this same name in the MUF log:
DB00201I - MULTI-USER ENABLED, CXX=CA11MUF MUFNAME=ADMUF1J AD
The easiest way to correct this mismatch is to rerun the assemble of the DBSIDPR module (using the appropriate AXCUS* or BDCUS* job), ensuring that the CXXNAME is set to the value shown in the DBUTLTY job or the DB00201 message as seen above.
As always, please contact Broadcom support for Datacom if you have further questions.