I am installing the CA Datacom/AD software for version 14.0, and want to know what the XCF_FROM setting is for and how to create the name. I would alsolike to understand what else I need to set up in order to use XCF with the Multi-User Facility (called MUF).
This document will address the setup for the MUF Startup Option XCF_FROM groupname for version 14.0 of CA Datacom/AD (called AD), and CA Datacom/DB (calledDB). It will also discuss the steps needed to utilize XCF capability.
In XCF processing using a basic Sysplex (no coupling facility structures), the group name is a way to relate the various tasks that work together. With CA Datacom, it usually identifies the Multi-User Facility (called MUF) that will be accessed by applications on the same LPAR/image as the MUF, or from remote LPARs/images within the Sysplex.
XCF_FROM Group Name
The group name specified in the XCF_FROM MUF Startup Option:
- can consist of a single asterisk(*). If an asterisk is specified for the group name, the value specified for TOGROUP within the DBSIDPR module is used;
- can be 1-8 characters, beginning with a letter;
- should not begin with the letters A through I, nor begin with SYS, to avoid conflict with IBM names. These are not prohibited, but could cause unexpected results within Z/OS;
- should be different from the group name used by other unrelated MUFs;
- cannot be the same as a MUFPLEX name, if used;
- cannot be the same as the internal MUF name.
Setting up CA Datacom for XCF
Here is an overview of the things to do to set up the MUF to support both local and remote (XCF) processing.
- In the DBSIDPR assemble found in INSTJCL members AXCUS01(AD), or BDCUSNEW/BDCUSUPG(DB):
- Be sure the value of CONNECT_ALLOW_PRIORITY is (LOCAL,XCF) to run from multiple LPARs/images.
- Ensure that the value of TARGET_MUF_LIST is a name for the MUF that is unique in your environment.
- Ensure that the value of TOGROUP is different from that used for all other MUFs. The unique MUF name is very important to maintain data integrity.
- Once these changes are complete, reassemble DBSIDPR.
- In the MUF startup options found in CUSMAC members AXDATIN1/AXDATIN2(AD) or DBDATIN2(DB):
- Ensure that the value of the first parameter of MUF is set to the default asterisk (*) or is a unique name within your environment.
- Ensure that XCF_FROM is uncommented and that the value is set to asterisk(*) to use the DBSIDPR TOGROUP value, or that it is a unique name as discussed above.
- Ensure that the value of TASKS has an appropriate value in the 5th subparameter (XCF value) to support the number of tasks you will be running on all remote LPARs/images.
- To utilize XCF processing, be sure your base loadlib - CAAXLOAD(AD) or CABDLOAD(DB) - and CUSLIB files are APF authorized on all LPARs/images where your tasks will be running, and that you have loaded the CA Datacom PC Call routines (DBPCCPR/DBPCSPR) with CAS9/CAIRIM on each.
These points will cover the greatest majority of causes for remote LPARs/images to not connect to a MUF.
- For more information about connecting to the MUF using XCF, please refer to the CA Datacom/DB Database and System Administration Guide for version 14.0 , in the section "Establishing Communication with z/OS › Connecting Using Cross-System Coupling Facility (XCF)."
- For more information about the various DBSIDPR settings, please refer to the CA Datacom/DB Database and System Administration Guide for version 14.0 , in the section "Using the Multi-User Facility › Modifying DBSIDPR Parameters."
- For more information about setting or changing the MUF Startup Options, please refer to the CA Datacom/DB Database and System Administration Guide for version 14.0 , in the section "Using the Multi-User Facility › Modifying MUF Startup Options."
As always, please contact CA Technologies support for CA Datacom if you have further questions.