Resolving error DB00205E - MULTI-USER ERROR - 1211
search cancel

Resolving error DB00205E - MULTI-USER ERROR - 1211

book

Article ID: 32417

calendar_today

Updated On:

Products

Datacom Datacom/AD Datacom/DB

Issue/Introduction

We are installing Datacom/AD and receive this error when trying to start the Multi-user (MUF) for the first time: 

  DB00205E - MULTI-USER ERROR 1211 CXXNAME CXXPROD VS CXX0NAME

What does this error mean, and how do we correct it?

Environment

Component : Datacom/AD

Component : Datacom/DB

Resolution

The last part of the DB00205E message gives the clue for this problem, which is that there is a mismatch of the CXX names you have specified for this MUF installation:

  CXXNAME xxxxxxxx VS yyyyyyyy

xxxxxxxx in the message is the CXX name provided in the DBSIDPR module.
yyyyyyyy is the CXX name in the CXX being used. The names do not match.

For example, given the message DB00205E - MULTI-USER ERROR - 1211 CXXNAME CXXPROD VS CXX0NAME:

rIn the INSTJCL customization job AXCUSNEW (Datacom/AD) or BDCUSNEW (Datacom/DB), you have coded "CXXPROD" as the value for "CXXNAME=" in the DBSIDPR macro, but you coded "CXXNAME=CXX0NAME" in the job that actually initialized the CXX (AXNEW01 for Datacom/AD, BDNEW01 for Datacom/DB).

To correct this, rerun the AXNEW01 or BDNEW01 job, and specify CXXNAME=* on the INIT AREA=CXX command (this is how the product is delivered). For example: 

INIT AREA=CXX,DATACOM=AD,CXXNAME=*

"*" means the CXX name will be taken from the DBSIDPR (in this example, it would be CXXPROD)

Additional Information

To find out what is specified in your DBSIDPR module, run a DBUTLTY job (there are several examples of this step in the INSTJCL PDS) with the following input:

//SYSIN DD *
SET OPTION1=ON-ERROR-CONTINUE
SET OPTION1=DUMPSID=DBSIDPR
SET OPTION1=DUMPPGM=DBSIDPR

/*
There are two commands here, and one of these should work for your version; the other one will be ignored.

Further information on the DBSIDPR parameters can be found in the documentation section titled "Modifying DBSIDPR Parameters."

As always, please contact Broadcom support for Datacom if you have further questions.