Resolving Datacom DB00912E SYSPLEX mismatch error
search cancel

Resolving Datacom DB00912E SYSPLEX mismatch error

book

Article ID: 21112

calendar_today

Updated On:

Products

Datacom Datacom/AD Datacom/DB

Issue/Introduction

When starting the MUF, I received errors about the SYSPLEX name:

DB00912E - CXX SYSPLEX x DOES NOT MATCH CURRENT SYSPLEX y
DB00501E - OPEN ERROR - RETURN CODE 47 (008) CXX=cxxname  (CXX     )

How do I change the SYSPLEX name in the CA Datacom Multi-user (MUF) and the CXX to correct this?

Environment

Release : 15.0

Release : 15.1

Component : CA Datacom/AD

Component : CA Datacom/DB

Cause

Executing the MUF on an LPAR different from the LPAR where the installation jobs were run.

Resolution

The SYSPLEX name is stored in the CXX of each MUF when the CXX is initialized and it can be verified by either running a DBUTLTY REPORT MEMORY=MVS function or looking in the MUF's JESMSGLG for the  message DB00905I.
In order to correct the SYSPLEX name, both the MUF and the applications using the MUF must not be running.

There are two ways to update the CXX with the correct SYSPLEX name: 

  1. Run DBUTLTY with this input:
    //SYSIN    DD  *
    CXXMAINT OPTION=ALTER,OPTION2=MATCHSID
    /*
    This will assume the SYSPLEX name from the system where the job was run.

  2. Run DBUTLTY with this input:
    //SYSIN    DD  *
    CXXMAINT OPTION=ALTER,OPTION2=MATCHSID,OUTNAME=sysplex-name
    /*

    This will assume the SYSPLEX name from the system where the job was run. Sysplex-name must be the SYSPLEX name for the LPAR where the MUF will execute.

Additional Information

This DBUTLTY job must run with the MUF down. Otherwise, the job will receive this error:

DB10053E - MUF RUNNING, FUNCTION REQUIRES MUF DOWN 

For more information about the CXXMAINT function, please refer to the CA Datacom documentation for CXXMAINT ALTER OPTION2.

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