CA Datacom/AD Version 15.0 Active Upgrade was successful but any subsequent attempt to access my CA product's data results in DB01410E - DATA SET NAME WRONG CXXNAME

Products

• Datacom
• DATACOM - AD

Issue/Introduction

Issue: 

CA Datacom/AD Version 15.0 Active Upgrade was successful but any subsequent attempt to access my CA product's data such as a DBUTLTY BACKUP of CA WORKLOAD AUTOMATION RESTART OPTION FOR Z/OS (aka CA-11) base 601 fails with:

DB01410E - DATA SET NAME WRONG CXXNAME DSN601 my.existing.dsn.DSN601

DB00501E - OPEN ERROR - RETURN CODE 76 (013) CXX=cxxname (DSN00601) 

The CA Datacom/AD 15.0 Multi-user (MUF) log shows...

DB00903I - OPENED, BASE -   601

DB01410E - DATA SET NAME WRONG CXXNAME IXX601 .

 

Environment:

z/OS 

Cause:

CA Datacom/AD 15.0 Active Upgrade job INSTJCL(AXACTUPG) STEP2A assembly of the custom module DBSIDPR specified "FORCE_DSN_CXXNAME=YES".

With "FORCE_DSN_CXXNAME=YES", the CXXNAME is enforced and requires that every data set that Datacom opens has the CXXNAME as a DSN node.

With 'FORCE_DSN_CXXNAME=NO' the CXXNAME name is not enforced as a node in the DSN.

Resolution: 

In job AXACTUPG STEP2A, change to "FORCE_DSN_CXXNAME=NO",

Rerun AXACTUPG to recreate the custom libraries.

Cycle the MUF to have the new DBSIDPR take effect.

 

Additional Information:

Refer to the CA Datacom® Core - 15.0 documentation section "Modifying DBSIDPR Parameters"

https://docops.ca.com/ca-datacom/15-0/en/administrating/ca-datacom-db-database-and-system-administration/using-the-multi-user-facility/modifying-dbsidpr-parameters#ModifyingDBSIDPRParameters-FORCE_DSN_CXXNAME=

 

Refer to CA Datacom® Messages

 

-- For error...

DB01410E - DATA SET NAME WRONG CXXNAME DSN601 my.existing.dsn.DSN601

    ... refer to...

DB01410E DATA SET NAME WRONG CXXNAME x y z

 

-- For error DB00501E - OPEN ERROR - RETURN CODE 76 (013) CXX=cxxname (DSN00601) 

   ... refer to...

Return Code 76 - OPEN ERROR 013 CONFLICT DBSIDPR DSN

 

 

 

 

Environment

Release:
Component: AD