Starting Your Product › Installation in the SYSPLEX Environment

Previous Topic: CA Datacom/AD Environment

Next Topic: Sample JCL Data Sets

Installation in the SYSPLEX Environment

When installing in a SYSPLEX environment, add the appropriate JOBPARM or ROUTE XEQ statement to ensure that the installation jobs are consistently executed on the appropriate processor.

In a SYSPLEX environment, make the CXX name unique. A unique CXX name is not only a best practice but a requirement for using the Simply feature in CA Datacom/AD Version 14.0. To simplify naming standards, give the CA Datacom/AD MUF name and the CXX name the same value.

A valid CXX name can be 8 bytes in length. We recommend that you make the name 1 to 7 bytes long and use the eighth byte for the Data Sharing or MUFplex feature.

You can discover what CXX names are in use by each LPAR by running a DBUTLTY JOB using REPORT MEMORY=MVS as the SYSIN value. If all the MUFs have been enabled since the last IPL of that LPAR, the MEMORY=MVS report contains the complete list of MUFs for that LPAR. This report is complete only after all the available MUFs have been started on a given LPAR after IPL. If you run this report before any MUF is started, that CXX name will be missing from the report.

A column in the MEMORY=MVS report has a heading of CXX Name. Use that column to collect the values that are in use for all LPARs. CA Datacom forces an enqueue action on the CXX SYSPLEX wide for CA Datacom/AD. A good practice is a unique name for all CXX names for your site. Starting with CA Datacom/AD Version 14.0, the CXX name has no default value, therefore you must determine that unique value yourself.

CXX^NAME is symbolic for the CXX name.

The DBSIDPR parameter FORCE_DSN_CXXNAME=NO is the recommended default because of the need for the majority of existing CA Datacom/AD sites to port or migrate their existing application database from the Version 10.0, 11.0, or 12.0 CA Datacom/AD source MUF. Those data sets often do not use the CXX name as one of the data set nodes. Therefore, this feature is turned off. If you have this feature turned on in DBSIDPR and the physical open is attempted with a data set that has no matching data set node to the CXX name, the open fails.