search cancel

CA 7 7CHAR_CXX_NAME for Datacom/AD CXX name

book

Article ID: 190071

calendar_today

Updated On:

Products

DATACOM - AD CA 7 Workload Automation

Issue/Introduction

How many characters for the CA Datacom/AD CXX name should be used for the CA Workload Automation CA 7 MUF?
The CA 7 documentation says use 7 characters and the CA Datacom/AD documentation says 1 to 7 bytes long. 

Environment

CA Datacom/AD 15.1 15.0
CA WORKLOAD AUTOMATION CA 7® EDITION 12.1

Cause

The CA WORKLOAD AUTOMATION CA 7® EDITION 12.1 documentation section "CA Datacom/AD DBSIDPR Values for CA 7" says:

"...Assemble DBSIDPR values, including changes for DELAY68, DELAY85, XCF access, TOGROUP, CONNECT_ALLOW_PRIORITY, and the TARGET MUF LIST. ... Replace the 7CHAR_CXX_NAME shown in the following sample with your choice of a seven character long CXXNAME that is unique to each MUF in your environment. Coordinate the values with other products using this CA Datacom/AD MUF:


 TITLE 'DATACOM/DB - DBSIDPR FOR INDIVIDUAL LOGICAL MUF' 
 DBSYSID                                                                X 
       SIMPLIFY_MODE=YES,                                               X 
       CXXNAME=7CHAR_CXX_NAME, NAME OF THE CXX                          X 
       DSN_XXX=HLQ.7CHAR_CXX_NAME.???,                                  X 
       FORCE_DSN_CXXNAME=NO, YES OR NO                                  X 
       CONSOLE_MINUTES=2, TIME BETWEEN AUTOMATIC STATUS CMDS            X 
       DELAY68=0,                                                       X 
       DELAY85=0,                                                       X 
       DELAY_DBUTLTY_SECURITY=NO, EXTERNAL SECURE YES/NO                X 
       TARGET_MUF_LIST=(7CHAR_CXX_NAME),                                X 
       TOGROUP=7CHAR_CXX_NAME,                                          X 
       CONNECT_ALLOW_PRIORITY=(LOCAL,XCF) 
END
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/automation/ca-workload-automation-ca-7-edition/12-1/installing-and-upgrading/start-your-product/configure-ca-datacom-ad-for-use-with-ca-wa-ca-7-edition.html


The CA DATACOM/AD 15.1 documentation section "Installation in the SYSPLEX Environment" says:
"...A valid CXX name can be 8 bytes in length. We recommend that you make the name 1 to 7 bytes long. Use the eighth byte for the Data Sharing or MUFplex feature.
...9CXX_NAME is symbolic for the CXX name. ..."
So, 7 characters is suggested to allow the 8th character as suffix in the TARGET_MUF_LIST when setting up for a SHADOW MUF.

Resolution

So, 7 characters is suggested to allow the 8th character as suffix in the TARGET_MUF_LIST when setting up for a Shadow MUF.

Additional Information

From the comments in the Datacom/AD 15.1 INSTJCL job AXCUSNEW:
...
//*  MUF NAME AND CXX NAME are being implemented with the same value.  
//*  That value should be 1-7 characters in length.  When you do the   
//*  global change for 9CXX_NAME to the new value the MUF NAME and CXX 
//*  NAME will match. This is recommended for SIMPLIFY.
...
TITLE 'DATACOM/DB - DBSIDPR FOR INDIVIDUAL LOGICAL MUF'        
        DBSYSID                                                       X
              SIMPLIFY_MODE=YES,    YES/NO                            X
              CXXNAME=9CXX_NAME,    NAME OF THE CXX                   X
              DSN_XXX=CAI.NEWHLQ.9CXX_NAME.???,                       X
              FORCE_DSN_CXXNAME=NO,   YES OR NO                       X
              CONSOLE_MINUTES=2,  TIME BETWEEN AUTOMATIC STATUS CMDS  X
              DELAY68=2,                                              X
              DELAY85=1,                                              X
              DELAY_DBUTLTY_SECURITY=NO,   EXTERNAL SECURE YES/NO     X
              TARGET_MUF_LIST=(9CXX_NAME),                            X
              CONNECT_ALLOW_PRIORITY=(LOCAL)                           
        END

For more on Shadow MUF, refer to
Article 27261 "How to use and configure a CA Datacom Shadow MUF."
https://ca-broadcomcsm.wolkenservicedesk.com/wolken/esd/knowledgebase_search?articleId=27261