How to configure the CA Datacom version 12.0 MUF for XCF use.

book

Article ID: 38204

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

Introduction:

In order to access a CA Datacom Multi-User Facility (called MUF) from an LPAR in the Sysplex other than where the MUF is running, it is necessary to define a number of parameters to the MUF to support XCF (IBM Cross-system Coupling Facility).

This document describes what is needed.

Environment: 

This applies to z/OS systems.

Instructions: 

Here are a few things that you need to do to set up your MUF in support of both local and remote (XCF) processing:

1. In your DBSIDPR assemble (found in INSTJCL member AXCUS01(CA Datacom/AD) or BDCUS01 (CA Datacom/DB) ), you need to have the setting CONNECT_ALLOW_PRIORITY=(LOCAL,XCF) to run from multiple LPARs.

2. In the same DBSIDPR, you need to ensure you have a unique name for the MUF in TARGET_MUF_LIST=(), and that you are using a different TOGROUP from any other MUF. The unique MUF name is very important to keep your data integrity. When you make these changes, reassemble DBSIDPR.

3. In your MUF startup options (CUSMAC member DBDATIN1), ensure that the "MUF" option has an asterisk (*) in the first parameter.

4. In the MUF options, be sure that XCFFROM is uncommented and that the XCF group name has the same value as the TOGROUP from DBSIDPR.

5. In the MUF options, be sure the TASKS option has an appropriate value in the 5th parameter (XCF value) to support the number of tasks you will be running on remote LPARs for your base product. Many clients will set this to at least 50-80 percent of the total TASKS value.

6. To utilize XCF processing, be sure your CAAXLOAD (/AD) or CABDLOAD (/DB) and your CUSLIB files are APF authorized on all LPARs where your tasks are running, and that you have loaded the SVC with CAS9/CAIRIM on those LPARs.

 In summary, you need:

DBSIDPR assembly (INSTJCL Member AXCUS01/BDCUS01):

  • CONNECT_ALLOW_PRIORITY=(LOCAL,XCF)
  • TOGROUP=<<1-8 character unique group name that you create>>
  • TARGET_MUF_LIST=<<1-7 character unique MUF/CXX name that you create>>

*  Note that the MUF name must be different from the TOGROUP name and in the case of a Shadow MUF, both MUFs have the same 1-7 root name plus a one-character suffix.

MUF startup options (CUSMAC member DBDATIN1):

  • XCF_FROM  *,*,GROUPNAME,YES  <<groupname matches TOGROUP above>>
  • MUF       *,99,NO            <<first value should be *>>
  • TASKS     250,32K,0,0,100    << 5th value must be greater than 0>>

These points will cover the greatest majority of causes for remote LPARs to not connect to a MUF. 

Additional Information:

For more information about using XCF with the MUF, please refer to the following Guide:

CA Datacom/DB version 12.0 Database and System Administration Guide, in the section “Establishing Communication with z/OS › Connecting Using Cross-System Coupling Facility (XCF)”

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

Environment

Release:
Component: DB